From: Guenter Roeck <linux@roeck-us.net>
To: Stafford Horne <shorne@gmail.com>
Cc: Jonas Bonn <jonas@southpole.se>,
openrisc@lists.librecores.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] openrisc: io: Define iounmap argument as volatile
Date: Fri, 29 Jul 2022 08:23:35 -0700 [thread overview]
Message-ID: <20220729152335.GA431060@roeck-us.net> (raw)
In-Reply-To: <20220729110726.3635262-1-shorne@gmail.com>
On Fri, Jul 29, 2022 at 08:07:25PM +0900, Stafford Horne wrote:
> When OpenRISC enables PCI it allows for more drivers to be compiled
> resulting in exposing the following with -Werror.
>
> drivers/video/fbdev/riva/fbdev.c: In function 'rivafb_probe':
> drivers/video/fbdev/riva/fbdev.c:2062:42: error:
> passing argument 1 of 'iounmap' discards 'volatile' qualifier from pointer target type
>
> drivers/video/fbdev/nvidia/nvidia.c: In function 'nvidiafb_probe':
> drivers/video/fbdev/nvidia/nvidia.c:1414:20: error:
> passing argument 1 of 'iounmap' discards 'volatile' qualifier from pointer target type
>
> drivers/scsi/aic7xxx/aic7xxx_osm.c: In function 'ahc_platform_free':
> drivers/scsi/aic7xxx/aic7xxx_osm.c:1231:41: error:
> passing argument 1 of 'iounmap' discards 'volatile' qualifier from pointer target type
>
> Most architectures define the iounmap argument to be volatile. To fix this
> issue we do the same for OpenRISC. This patch must go before PCI is enabled on
> OpenRISC to avoid any compile failures.
>
> Link: https://lore.kernel.org/lkml/20220729033728.GA2195022@roeck-us.net/
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Signed-off-by: Stafford Horne <shorne@gmail.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
> ---
> arch/openrisc/include/asm/io.h | 2 +-
> arch/openrisc/mm/ioremap.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/openrisc/include/asm/io.h b/arch/openrisc/include/asm/io.h
> index 625ac6ad1205..ee6043a03173 100644
> --- a/arch/openrisc/include/asm/io.h
> +++ b/arch/openrisc/include/asm/io.h
> @@ -31,7 +31,7 @@
> void __iomem *ioremap(phys_addr_t offset, unsigned long size);
>
> #define iounmap iounmap
> -extern void iounmap(void __iomem *addr);
> +extern void iounmap(volatile void __iomem *addr);
>
> #include <asm-generic/io.h>
>
> diff --git a/arch/openrisc/mm/ioremap.c b/arch/openrisc/mm/ioremap.c
> index daae13a76743..8ec0dafecf25 100644
> --- a/arch/openrisc/mm/ioremap.c
> +++ b/arch/openrisc/mm/ioremap.c
> @@ -77,7 +77,7 @@ void __iomem *__ref ioremap(phys_addr_t addr, unsigned long size)
> }
> EXPORT_SYMBOL(ioremap);
>
> -void iounmap(void __iomem *addr)
> +void iounmap(volatile void __iomem *addr)
> {
> /* If the page is from the fixmap pool then we just clear out
> * the fixmap mapping.
> --
> 2.37.1
>
prev parent reply other threads:[~2022-07-29 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 11:07 [PATCH] openrisc: io: Define iounmap argument as volatile Stafford Horne
2022-07-29 15:23 ` Guenter Roeck [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=20220729152335.GA431060@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.org \
--cc=shorne@gmail.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 NNTP newsgroup(s).