Hi, As I was alluding to in this email:
http://lists.infradead.org/pipermail/lede-dev/2017-February/005980.html there used to be a problem in that we could not load kernel modules. This was largely fixed by two different commits: 1f12a3daaaa8f3525741bef2bc2be7c5c6c77b50 ("kernel: speed up build system by getting rid of redundant work") 0df2c6563a3537ed21b28a9fb6874bf2718afd05 ("kernel: prevent addition of scm marker to localversion") However this solves the problems by just completely overriding KERNELRELEASE and we lose any kind of valuable information in there. When doing external kernel builds, which are usually reflective of doing kernel work, it is very important to have a correct kernel version string (as reported by uname) just like keeping modules to load is important. This patch series addresses that by properly determining what the modules installation directory should be. Florian Fainelli (3): Revert "kernel: prevent addition of scm marker to localversion" include: Do not alter KERNELRELEASE for external/git kernels include: Determine MODULES_DIR correctly for external/git kernels include/kernel-defaults.mk | 11 ++++++----- include/kernel.mk | 8 +++++--- 2 files changed, 11 insertions(+), 8 deletions(-) -- 2.12.2 _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
