From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>, Frank Li <Frank.Li@nxp.com>,
Jorge Marques <jorge.marques@analog.com>,
linux-i3c@lists.infradead.org
Subject: Re: [PATCH] i3c: remove 'const' from FIFO helpers
Date: Thu, 7 Aug 2025 22:21:42 +0200 [thread overview]
Message-ID: <2025080720214218750df5@mail.local> (raw)
In-Reply-To: <20250807043456.1624-2-wsa+renesas@sang-engineering.com>
On 07/08/2025 06:31:24+0200, Wolfram Sang wrote:
> As buildbot reports, some architectures do not want const pointers.
>
> Fixes: 733b439375b4 ("i3c: master: Add inline i3c_readl_fifo() and i3c_writel_fifo()")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202508070438.TZZA3f2S-lkp@intel.com/
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> I still wonder why SPARC discards the const but since nobody seems to be
> commenting on that, I guess the fastest way to get the build error out
> of Linus' tree is to adapt the usage in I3C.
>
My plan was to let sparc people handle their mess, there is no reason
const should be discarded.
> drivers/i3c/internals.h | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/i3c/internals.h b/drivers/i3c/internals.h
> index 0d857cc68cc5..2b0b9c3a9131 100644
> --- a/drivers/i3c/internals.h
> +++ b/drivers/i3c/internals.h
> @@ -30,8 +30,7 @@ void i3c_dev_free_ibi_locked(struct i3c_dev_desc *dev);
> * @buf: Pointer to the data bytes to write
> * @nbytes: Number of bytes to write
> */
> -static inline void i3c_writel_fifo(void __iomem *addr, const void *buf,
> - int nbytes)
> +static inline void i3c_writel_fifo(void __iomem *addr, void *buf, int nbytes)
> {
> writesl(addr, buf, nbytes / 4);
> if (nbytes & 3) {
> @@ -48,8 +47,7 @@ static inline void i3c_writel_fifo(void __iomem *addr, const void *buf,
> * @buf: Pointer to the buffer to store read bytes
> * @nbytes: Number of bytes to read
> */
> -static inline void i3c_readl_fifo(const void __iomem *addr, void *buf,
> - int nbytes)
> +static inline void i3c_readl_fifo(void __iomem *addr, void *buf, int nbytes)
> {
> readsl(addr, buf, nbytes / 4);
> if (nbytes & 3) {
> --
> 2.47.2
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>, Frank Li <Frank.Li@nxp.com>,
Jorge Marques <jorge.marques@analog.com>,
linux-i3c@lists.infradead.org
Subject: Re: [PATCH] i3c: remove 'const' from FIFO helpers
Date: Thu, 7 Aug 2025 22:21:42 +0200 [thread overview]
Message-ID: <2025080720214218750df5@mail.local> (raw)
In-Reply-To: <20250807043456.1624-2-wsa+renesas@sang-engineering.com>
On 07/08/2025 06:31:24+0200, Wolfram Sang wrote:
> As buildbot reports, some architectures do not want const pointers.
>
> Fixes: 733b439375b4 ("i3c: master: Add inline i3c_readl_fifo() and i3c_writel_fifo()")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202508070438.TZZA3f2S-lkp@intel.com/
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> I still wonder why SPARC discards the const but since nobody seems to be
> commenting on that, I guess the fastest way to get the build error out
> of Linus' tree is to adapt the usage in I3C.
>
My plan was to let sparc people handle their mess, there is no reason
const should be discarded.
> drivers/i3c/internals.h | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/i3c/internals.h b/drivers/i3c/internals.h
> index 0d857cc68cc5..2b0b9c3a9131 100644
> --- a/drivers/i3c/internals.h
> +++ b/drivers/i3c/internals.h
> @@ -30,8 +30,7 @@ void i3c_dev_free_ibi_locked(struct i3c_dev_desc *dev);
> * @buf: Pointer to the data bytes to write
> * @nbytes: Number of bytes to write
> */
> -static inline void i3c_writel_fifo(void __iomem *addr, const void *buf,
> - int nbytes)
> +static inline void i3c_writel_fifo(void __iomem *addr, void *buf, int nbytes)
> {
> writesl(addr, buf, nbytes / 4);
> if (nbytes & 3) {
> @@ -48,8 +47,7 @@ static inline void i3c_writel_fifo(void __iomem *addr, const void *buf,
> * @buf: Pointer to the buffer to store read bytes
> * @nbytes: Number of bytes to read
> */
> -static inline void i3c_readl_fifo(const void __iomem *addr, void *buf,
> - int nbytes)
> +static inline void i3c_readl_fifo(void __iomem *addr, void *buf, int nbytes)
> {
> readsl(addr, buf, nbytes / 4);
> if (nbytes & 3) {
> --
> 2.47.2
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-08-07 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 4:31 [PATCH] i3c: remove 'const' from FIFO helpers Wolfram Sang
2025-08-07 4:31 ` Wolfram Sang
2025-08-07 20:21 ` Alexandre Belloni [this message]
2025-08-07 20:21 ` Alexandre Belloni
2025-08-08 9:43 ` Geert Uytterhoeven
2025-08-08 9:43 ` Geert Uytterhoeven
2025-08-08 11:18 ` Arnd Bergmann
2025-08-08 11:18 ` Arnd Bergmann
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=2025080720214218750df5@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=Frank.Li@nxp.com \
--cc=jorge.marques@analog.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.