Re: [PATCH] kbuild: warn a relative path used for M= in out-of-tree builds

CC: kernel-t...@android.com Thanks Masahiro! I'd like to also note that the Android kernel build system is leveraging this behaviour as sort of an "O=" for external modules [1]. This way the external module's build artifacts are contained separate from the kernel build artifacts and the module's

[PATCH] kbuild: warn a relative path used for M= in out-of-tree builds

Surprising to me, Kbuild can handle a relative M= path while having in-kernel objects in a separate directory. In this case, the M= option actually defines: - the path to external module sources relative to $(srctree) - the path to external module objects relative to $(objtree) For example,