From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Kees Cook" <kees@kernel.org>,
"Palmer Dabbelt" <palmer@rivosinc.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: Linux-Arch <linux-arch@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iomap: Fix -Wmissing-prototypes on UM
Date: Mon, 03 Feb 2025 09:18:33 +0100 [thread overview]
Message-ID: <15b87c5f-92de-4201-9c67-a93d5dcefe68@app.fastmail.com> (raw)
In-Reply-To: <20250203-um-io-v1-1-822af81bcdac@linutronix.de>
On Mon, Feb 3, 2025, at 08:26, Thomas Weißschuh wrote:
> Building lib/iomap.o on UM triggers warnings about missing prototypes.
> These prototypes should be defined by asm-generic/iomap.h, depending on
> other symbols. For example "ioread64_lo_hi" is based on "readq".
> However the generic variants of those tested symbols are defined in
> asm-generic/io.h, only after asm-generic/iomap.h has already been
> included, breaking the ifdef logic.
Sorry I never took the time to fix this so far.
> --- a/include/asm-generic/io.h
> +++ b/include/asm-generic/io.h
> @@ -13,10 +13,6 @@
> #include <linux/types.h>
> #include <linux/instruction_pointer.h>
>
> -#ifdef CONFIG_GENERIC_IOMAP
> -#include <asm-generic/iomap.h>
> -#endif
> -
> #include <asm/mmiowb.h>
> #include <asm-generic/pci_iomap.h>
>
> @@ -1250,4 +1246,8 @@ extern int devmem_is_allowed(unsigned long pfn);
>
> #endif /* __KERNEL__ */
>
> +#ifdef CONFIG_GENERIC_IOMAP
> +#include <asm-generic/iomap.h>
> +#endif
> +
> #endif /* __ASM_GENERIC_IO_H */
I have not tried it yet, but I suspect this is not the correct
fix here. Unfortunately the indirect header inclusions in this
file are way too complicated with corner cases in various
architectures. How much testing have you given your patch
across other targets? I think the last time we tried to address
it, we broke mips or parisc.
Arnd
next prev parent reply other threads:[~2025-02-03 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 7:26 Thomas Weißschuh
2025-02-03 8:18 ` Arnd Bergmann [this message]
2025-02-03 8:25 ` Thomas Weißschuh
2025-02-03 11:43 ` Arnd Bergmann
2025-02-03 12:07 ` Andy Shevchenko
2025-02-03 13:08 ` Arnd Bergmann
2025-02-03 13:23 ` Andy Shevchenko
2025-02-03 13:34 ` Arnd Bergmann
2025-02-03 14:29 ` Andy Shevchenko
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=15b87c5f-92de-4201-9c67-a93d5dcefe68@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=kees@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=palmer@rivosinc.com \
--cc=thomas.weissschuh@linutronix.de \
/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
all inboxes | Powered by JetHome®