From: Andreas Larsson <andreas@gaisler.com>
To: Al Viro <viro@zeniv.linux.org.uk>, sparclinux@vger.kernel.org
Cc: linux-arch@vger.kernel.org
Subject: Re: [PATCH] fix prototypes of reads[bwl]() on sparc64
Date: Fri, 19 Sep 2025 20:02:58 +0200 [thread overview]
Message-ID: <fbb1a96c-d913-4bdf-b40c-c8981601bbf9@gaisler.com> (raw)
In-Reply-To: <20250810034208.GJ222315@ZenIV>
On 2025-08-10 05:42, Al Viro wrote:
> Conventions for readsl() are the same as for readl() - any __iomem
> pointer is acceptable, both const and volatile ones being OK. Same
> for readsb() and readsw().
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> ---
> diff --git a/arch/sparc/include/asm/io_64.h b/arch/sparc/include/asm/io_64.h
> index c9528e4719cd..d8ed296624af 100644
> --- a/arch/sparc/include/asm/io_64.h
> +++ b/arch/sparc/include/asm/io_64.h
> @@ -250,19 +250,19 @@ void insl(unsigned long, void *, unsigned long);
> #define insw insw
> #define insl insl
>
> -static inline void readsb(void __iomem *port, void *buf, unsigned long count)
> +static inline void readsb(const volatile void __iomem *port, void *buf, unsigned long count)
> {
> insb((unsigned long __force)port, buf, count);
> }
> #define readsb readsb
>
> -static inline void readsw(void __iomem *port, void *buf, unsigned long count)
> +static inline void readsw(const volatile void __iomem *port, void *buf, unsigned long count)
> {
> insw((unsigned long __force)port, buf, count);
> }
> #define readsw readsw
>
> -static inline void readsl(void __iomem *port, void *buf, unsigned long count)
> +static inline void readsl(const volatile void __iomem *port, void *buf, unsigned long count)
> {
> insl((unsigned long __force)port, buf, count);
> }
Reviewed-by: Andreas Larsson <andreas@gaisler.com>
Picking this up to my for-next.
Thanks,
Andreas
next prev parent reply other threads:[~2025-09-19 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 3:42 [PATCH] fix prototypes of reads[bwl]() on sparc64 Al Viro
2025-09-19 18:02 ` Andreas Larsson [this message]
2025-09-19 18:58 ` Andreas Larsson
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=fbb1a96c-d913-4bdf-b40c-c8981601bbf9@gaisler.com \
--to=andreas@gaisler.com \
--cc=linux-arch@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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