Macro MODULE depends on how file is compiled, extracted from build system #35
Description
Issue occured in security/smack/smackfs, where MODULE is handled incorrectly
incorrect handling of CONFIG_MODULES
the whole file can only be compiled in obj-y or obj-n because CONFIG_SECURITY_SMACK is a boolean option. That is, within that file MODULE can never be active.
However, currently MODULE is linked to CONFIG_MODULES and not whether the the specific file is compiled as a module or not. That would require a different extraction from the build system and different handling of the MODULE macro