From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the percpu tree
Date: Mon, 11 Dec 2023 17:14:06 +1100 [thread overview]
Message-ID: <20231211171406.71fdc29b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]
Hi all,
After merging the percpu tree, today's linux-next build (sparc64
defconfig) failed like this:
mm/percpu.c: In function 'pcpu_page_first_chunk':
mm/percpu.c:3336:17: error: implicit declaration of function 'flush_cache_vmap_early'; did you mean 'flush_cache_vmap'? [-Werror=implicit-function-declaration]
3336 | flush_cache_vmap_early(unit_addr, unit_addr + ai->unit_size);
| ^~~~~~~~~~~~~~~~~~~~~~
| flush_cache_vmap
cc1: some warnings being treated as errors
Caused by commit
a95c15a43f4a ("mm: Introduce flush_cache_vmap_early() and its riscv implementation")
I have applied the following fix patch for today. Are there other
archs that don't use asm-generic/cacheflush.h?
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 11 Dec 2023 16:57:00 +1100
Subject: [PATCH] fix up for "mm: Introduce flush_cache_vmap_early() and its riscv implementation"
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
arch/sparc/include/asm/cacheflush.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/sparc/include/asm/cacheflush.h b/arch/sparc/include/asm/cacheflush.h
index 881ac76eab93..9d87b2bcb217 100644
--- a/arch/sparc/include/asm/cacheflush.h
+++ b/arch/sparc/include/asm/cacheflush.h
@@ -10,4 +10,11 @@
#else
#include <asm/cacheflush_32.h>
#endif
+
+#ifndef __ASSEMBLY__
+static inline void flush_cache_vmap_early(unsigned long start, unsigned long end)
+{
+}
+#endif
+
#endif
--
2.40.1
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-12-11 6:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 6:14 Stephen Rothwell [this message]
2023-12-11 8:31 ` linux-next: build failure after merge of the percpu tree Alexandre Ghiti
2023-12-11 19:25 ` Dennis Zhou
-- strict thread matches above, loose matches on Subject: below --
2018-02-26 3:57 Stephen Rothwell
2014-08-27 4:22 Stephen Rothwell
2011-01-04 4:21 Stephen Rothwell
2011-01-04 5:13 ` Tejun Heo
2011-01-06 4:18 ` Stephen Rothwell
2011-01-06 5:11 ` Tejun Heo
2010-09-10 2:45 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231211171406.71fdc29b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexghiti@rivosinc.com \
--cc=cl@linux-foundation.org \
--cc=dennis@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox