KBUILD_MODNAME is not defined for files that are linked into multiple modules, and trying to change reality to match documentation would result in all sorts of trouble. E.g. options for built-in modules would be called either foo_bar.param, foo.param, or bar.param, depending on the configuration. So just change the comment.
Showing the changes to scripts (1 of 1 file). Show all
Unified · Split
| @@ -93,9 +93,9 @@ obj-dirs := $(addprefix $(obj)/,$(obj-dirs)) · 92 unmodified lines | ||
| 93 | 93 | # already |
| 94 | 94 | # $(modname_flags) #defines KBUILD_MODNAME as the name of the module it will |
| 95 | 95 | # end up in (or would, if it gets compiled in) |
| 96 | −# Note: It's possible that one object gets potentially linked into more | |
| 97 | −# than one module. In that case KBUILD_MODNAME will be set to foo_bar, | |
| 98 | −# where foo and bar are the name of the modules. | |
| 96 | +# Note: Files that end up in two or more modules are compiled without the | |
| 97 | +# KBUILD_MODNAME definition. The reason is that any made-up name would | |
| 98 | +# differ in different configs. | |
| 99 | 99 | name-fix = $(subst $(comma),_,$(subst -,_,$1)) |
| 100 | 100 | basename_flags = -D"KBUILD_BASENAME=KBUILD_STR($(call name-fix,$(basetarget)))" |
| 101 | 101 | modname_flags = $(if $(filter 1,$(words $(modname))),\ |