From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Daniel Axtens <dja@axtens.net>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 4/6] powerpc/kernel: Clean up some sparse warnings
Date: Mon, 04 Jul 2016 09:50:23 +0200 [thread overview]
Message-ID: <5516741.DExtAhFdTo@wuerfel> (raw)
In-Reply-To: <1467616182-30886-4-git-send-email-dja@axtens.net>
On Monday, July 4, 2016 5:09:40 PM CEST Daniel Axtens wrote:
> diff --git a/arch/powerpc/kernel/io.c b/arch/powerpc/kernel/io.c
> index 2a2b4aeab80f..3f70b7dccee8 100644
> --- a/arch/powerpc/kernel/io.c
> +++ b/arch/powerpc/kernel/io.c
> @@ -37,7 +37,7 @@ void _insb(const volatile u8 __iomem *port, void *buf, long count)
> return;
> asm volatile("sync");
> do {
> - tmp = *port;
> + tmp = *(u8 __force *)port;
> eieio();
> *tbuf++ = tmp;
> } while (--count != 0);
Here the "volatile" is actually meaningful, you should keep it and
just add "__force" in addition.
> @@ -47,13 +47,13 @@ EXPORT_SYMBOL(_insb);
>
> void _outsb(volatile u8 __iomem *port, const void *buf, long count)
> {
> - const u8 *tbuf = buf;
> + const u8 __force *tbuf = buf;
>
> if (unlikely(count <= 0))
> return;
> asm volatile("sync");
> do {
> - *port = *tbuf++;
> + *(volatile u8 __force *)port = *tbuf++;
> } while (--count != 0);
> asm volatile("sync");
> }
like you correctly do here.
> @@ -68,7 +68,7 @@ void _insw_ns(const volatile u16 __iomem *port, void *buf, long count)
> return;
> asm volatile("sync");
> do {
> - tmp = *port;
> + tmp = *(u16 __force *)port;
> eieio();
> *tbuf++ = tmp;
> } while (--count != 0);
+volatile
> @@ -99,7 +99,7 @@ void _insl_ns(const volatile u32 __iomem *port, void *buf, long count)
> return;
> asm volatile("sync");
> do {
> - tmp = *port;
> + tmp = *(u32 __force *)port;
> eieio();
> *tbuf++ = tmp;
> } while (--count != 0);
+volatile
Arnd
next prev parent reply other threads:[~2016-07-04 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 7:09 [PATCH 1/6] powerpc/kvm: Clarify __user annotations Daniel Axtens
2016-07-04 7:09 ` [PATCH 2/6] powerpc/kernel: Drop annotation for generic, unannotated function Daniel Axtens
2016-07-04 7:09 ` [PATCH 3/6] powerpc/xics: Fully qualify cast to silence sparse Daniel Axtens
2016-07-04 7:27 ` Andrew Donnellan
2016-07-04 7:46 ` Arnd Bergmann
2016-07-04 7:09 ` [PATCH 4/6] powerpc/kernel: Clean up some sparse warnings Daniel Axtens
2016-07-04 7:50 ` Arnd Bergmann [this message]
2016-07-04 7:09 ` [PATCH 5/6] powerpc/sparse: Pass endianness to sparse Daniel Axtens
2016-07-04 7:32 ` Andrew Donnellan
2016-07-04 7:52 ` Arnd Bergmann
2016-07-04 7:09 ` [PATCH 6/6] powerpc/sparse: Make ppc_md.{halt, restart} __noreturn Daniel Axtens
2016-07-04 10:20 ` kbuild test robot
2016-07-04 7:26 ` [PATCH 1/6] powerpc/kvm: Clarify __user annotations Andrew Donnellan
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=5516741.DExtAhFdTo@wuerfel \
--to=arnd@arndb.de \
--cc=dja@axtens.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
/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).