summaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2013-04-23 18:30:43 +0200
committerDave Airlie <airlied@redhat.com>2013-04-26 10:18:46 +1000
commita59e1ff3b83726f581ba7a421af97bd1589d9e2c (patch)
treea6b3f9b2612a48ce5f9ec317cba14b023d1a3a91 /firmware
parent84806ade19fe07ad30049298d12c3e58eebb192d (diff)
downloadlinux-a59e1ff3b83726f581ba7a421af97bd1589d9e2c.tar.bz2
drm/tilcdc: use only a single module device table
The tilcdc driver fails to be built as a module because of extraneous MODULE_DEVICE_TABLE entries: drivers/gpu/drm/tilcdc/tilcdc_slave.o:(.data+0x54): multiple definition of `__mod_of_device_table' drivers/gpu/drm/tilcdc/tilcdc_tfp410.o:(.data+0x54): first defined here drivers/gpu/drm/tilcdc/tilcdc_panel.o:(.data+0x54): multiple definition of `__mod_of_device_table' drivers/gpu/drm/tilcdc/tilcdc_tfp410.o:(.data+0x54): first defined here drivers/gpu/drm/tilcdc/tilcdc_drv.o:(.data+0x184): multiple definition of `__mod_of_device_table' drivers/gpu/drm/tilcdc/tilcdc_tfp410.o:(.data+0x54): first defined here Since the entire point of these entries is to make the module autoload when one of the devices is present, it's enough to keep the one entry for "ti,am33xx-tilcdc", which should always be there if any of the others are. Acked-by: Rob Clark <robdclark@gmail.com> Cc: dri-devel@lists.freedesktop.org Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions