diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-05-07 02:28:17 +0900 |
---|---|---|
committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-05-07 21:50:24 +0900 |
commit | 4c11edfcf70bea4cb0a3f4992ac6a4852e8bdc31 (patch) | |
tree | 5f2c5fd65a460c3453de6fdec2a0184b14355213 /Documentation/trace | |
parent | 1e35663e41360adf564a91811b29cc7e56ee9c39 (diff) | |
download | linux-4c11edfcf70bea4cb0a3f4992ac6a4852e8bdc31.tar.gz linux-4c11edfcf70bea4cb0a3f4992ac6a4852e8bdc31.tar.bz2 linux-4c11edfcf70bea4cb0a3f4992ac6a4852e8bdc31.zip |
Remove MODULE_ALIAS() calls that take undefined macro
These files do not define (USBHS_)DRIVER_NAME. Yet, they can be
successfully compiled because they are never built as a module by
anyone, i.e, the MODULE_ALIAS() calls are always no-op.
A problem showed up when a patch "moduleparam: Save information about
built-in modules in separate file" was applied. With this new feature,
MODULE_*() will be populated even if the callers are built-in.
To avoid the build errors, the lines referencing to the undefined
macro must be removed.
The complete fix is to remove all MODULE_* and #include <linux/module.h>
like many "make ... explicitly non-modular" commits did.
For now, I am touching only the offending lines.
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Acked-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'Documentation/trace')
0 files changed, 0 insertions, 0 deletions