summaryrefslogtreecommitdiffstats
path: root/drivers/android/Makefile
diff options
context:
space:
mode:
authorPaul Gortmaker <paul.gortmaker@windriver.com>2015-06-15 15:12:47 -0700
committerBryan Wu <cooloney@gmail.com>2015-06-22 13:57:09 -0700
commitb83fae0c0c5ea97aad4f762dae99342f94523f42 (patch)
treea11cdacd3aede68ff5ac3997fbcbd8166fc739ef /drivers/android/Makefile
parentac69b9038f8214e2a8ee0eb3a113af473a7518e4 (diff)
downloadblackbird-obmc-linux-b83fae0c0c5ea97aad4f762dae99342f94523f42.tar.gz
blackbird-obmc-linux-b83fae0c0c5ea97aad4f762dae99342f94523f42.zip
drivers/leds: don't use module_init in non-modular leds-cobalt-raq.c
This file is built for a bool Kconfig variable, and hence this code is either present or absent. It currently can never be modular, so using module_init as an alias for __initcall can be somewhat misleading. Fix this up now, so that we can relocate module_init from init.h into module.h in the future. If we don't do this, we'd have to add module.h to obviously non-modular code, and that would be a worse thing. Note that direct use of __initcall is discouraged, vs. one of the priority categorized subgroups. As __initcall gets mapped onto device_initcall, our use of device_initcall directly in this change means that the runtime impact is zero -- it will remain at level 6 in initcall ordering. And since it can't be modular, we remove all the __exitcall stuff related to module_exit() -- it is dead code that won't ever be executed. Cc: Richard Purdie <rpurdie@rpsys.net> Cc: linux-leds@vger.kernel.org Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Acked-by: Jacek Anaszewski <j.anaszewski@samsung.com> Signed-off-by: Bryan Wu <cooloney@gmail.com>
Diffstat (limited to 'drivers/android/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud