The patch titled
Subject: m32r: fix build failure
has been added to the -mm tree. Its filename is
m32r-fix-build-failure.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/m32r-fix-build-failure.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/m32r-fix-build-failure.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
Subject: m32r: fix build failure
m32r allmodconfig build was failing with the error: ERROR:
"smp_flush_cache_all" [drivers/misc/lkdtm.ko] undefined!
lkdtm driver at drivers/misc is using flush_icache_range() which for m32r
is defined as smp_flush_cache_all() if CONFIG_SMP is defined. But as
smp_flush_cache_all() was not exported so the build was failing with the
error of undefined symbol.
Link: http://lkml.kernel.org/r/1464001182-8329-1-git-send-email-sudipm.mukherjee@xxxxxxxxx
Signed-off-by: Sudip Mukherjee <sudip.mukherjee@xxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
arch/m32r/kernel/smp.c | 1 +
1 file changed, 1 insertion(+)
diff -puN arch/m32r/kernel/smp.c~m32r-fix-build-failure arch/m32r/kernel/smp.c
--- a/arch/m32r/kernel/smp.c~m32r-fix-build-failure
+++ a/arch/m32r/kernel/smp.c
@@ -164,6 +164,7 @@ void smp_flush_cache_all(void)
spin_unlock(&flushcache_lock);
preempt_enable();
}
+EXPORT_SYMBOL(smp_flush_cache_all);
void smp_flush_cache_all_interrupt(void)
{
_
Patches currently in -mm which might be from sudipm.mukherjee@xxxxxxxxx are
m32r-fix-build-failure.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
