From: Nathan Chancellor <nathan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com,
Brian Cain <bcain@codeaurora.org>
Subject: Re: [PATCH] Hexagon: Export raw I/O routines for modules
Date: Wed, 4 Aug 2021 11:26:10 -0700 [thread overview]
Message-ID: <YQrbwnDf7KaiSMzF@Ryzen-9-3900X.localdomain> (raw)
In-Reply-To: <20210708233849.3140194-1-nathan@kernel.org>
Andrew, could you pick this up? Brian gave his ack and we just got a
0day report about this:
https://lore.kernel.org/r/202108041936.52T4sUU6-lkp@intel.com/
If you need me to resend this, I can.
Cheers,
Nathan
On Thu, Jul 08, 2021 at 04:38:50PM -0700, Nathan Chancellor wrote:
> When building ARCH=hexagon allmodconfig, the following errors occur:
>
> ERROR: modpost: "__raw_readsl" [drivers/i3c/master/svc-i3c-master.ko] undefined!
> ERROR: modpost: "__raw_writesl" [drivers/i3c/master/dw-i3c-master.ko] undefined!
> ERROR: modpost: "__raw_readsl" [drivers/i3c/master/dw-i3c-master.ko] undefined!
> ERROR: modpost: "__raw_writesl" [drivers/i3c/master/i3c-master-cdns.ko] undefined!
> ERROR: modpost: "__raw_readsl" [drivers/i3c/master/i3c-master-cdns.ko] undefined!
>
> Export these symbols so that modules can use them without any errors.
>
> Fixes: 013bf24c3829 ("Hexagon: Provide basic implementation and/or stubs for I/O routines.")
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> ---
>
> It would be nice if this could get into 5.14 at some point so that we
> can build ARCH=hexagon allmodconfig in our CI.
>
> arch/hexagon/lib/io.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/hexagon/lib/io.c b/arch/hexagon/lib/io.c
> index d35d69d6588c..55f75392857b 100644
> --- a/arch/hexagon/lib/io.c
> +++ b/arch/hexagon/lib/io.c
> @@ -27,6 +27,7 @@ void __raw_readsw(const void __iomem *addr, void *data, int len)
> *dst++ = *src;
>
> }
> +EXPORT_SYMBOL(__raw_readsw);
>
> /*
> * __raw_writesw - read words a short at a time
> @@ -47,6 +48,7 @@ void __raw_writesw(void __iomem *addr, const void *data, int len)
>
>
> }
> +EXPORT_SYMBOL(__raw_writesw);
>
> /* Pretty sure len is pre-adjusted for the length of the access already */
> void __raw_readsl(const void __iomem *addr, void *data, int len)
> @@ -62,6 +64,7 @@ void __raw_readsl(const void __iomem *addr, void *data, int len)
>
>
> }
> +EXPORT_SYMBOL(__raw_readsl);
>
> void __raw_writesl(void __iomem *addr, const void *data, int len)
> {
> @@ -76,3 +79,4 @@ void __raw_writesl(void __iomem *addr, const void *data, int len)
>
>
> }
> +EXPORT_SYMBOL(__raw_writesl);
>
> base-commit: f55966571d5eb2876a11e48e798b4592fa1ffbb7
> --
> 2.32.0.93.g670b81a890
prev parent reply other threads:[~2021-08-04 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 23:38 [PATCH] Hexagon: Export raw I/O routines for modules Nathan Chancellor
2021-07-28 0:18 ` Nathan Chancellor
2021-07-28 15:08 ` Brian Cain
2021-08-04 18:26 ` Nathan Chancellor [this message]
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=YQrbwnDf7KaiSMzF@Ryzen-9-3900X.localdomain \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bcain@codeaurora.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).