From: Daniel Axtens <dja@axtens.net>
To: linuxppc-dev@ozlabs.org
Cc: arnd@arndb.de, Daniel Axtens <dja@axtens.net>
Subject: [PATCH v2 2/5] powerpc/xics: Fully qualify cast to silence sparse
Date: Tue, 12 Jul 2016 10:54:49 +1000 [thread overview]
Message-ID: <1468284892-27765-2-git-send-email-dja@axtens.net> (raw)
In-Reply-To: <1468284892-27765-1-git-send-email-dja@axtens.net>
Make the cast fully line up with what out_rm8 expects.
Signed-off-by: Daniel Axtens <dja@axtens.net>
---
v2: Fix issues identified by Arnd.
---
arch/powerpc/sysdev/xics/icp-native.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/sysdev/xics/icp-native.c b/arch/powerpc/sysdev/xics/icp-native.c
index afdf62f2a695..6e47ddd374b2 100644
--- a/arch/powerpc/sysdev/xics/icp-native.c
+++ b/arch/powerpc/sysdev/xics/icp-native.c
@@ -176,7 +176,7 @@ void icp_native_cause_ipi_rm(int cpu)
* causing the IPI.
*/
xics_phys = paca[cpu].kvm_hstate.xics_phys;
- out_rm8((u8 *)(xics_phys + XICS_MFRR), IPI_PRIORITY);
+ out_rm8((u8 __iomem *)(xics_phys + XICS_MFRR), IPI_PRIORITY);
}
#endif
--
2.1.4
next prev parent reply other threads:[~2016-07-12 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 0:54 [PATCH v2 1/5] powerpc/kvm: Clarify __user annotations Daniel Axtens
2016-07-12 0:54 ` Daniel Axtens [this message]
2016-07-12 0:54 ` [PATCH v2 3/5] powerpc/kernel: Clean up some sparse warnings Daniel Axtens
2016-07-12 0:54 ` [PATCH v2 4/5] powerpc/sparse: Pass endianness to sparse Daniel Axtens
2016-07-15 10:53 ` [v2,4/5] " Michael Ellerman
2016-07-12 0:54 ` [PATCH v2 5/5] powerpc/sparse: Make ppc_md.{halt, restart} __noreturn Daniel Axtens
2016-07-15 10:53 ` [v2,5/5] " Michael Ellerman
2016-07-15 10:53 ` [v2,1/5] powerpc/kvm: Clarify __user annotations Michael Ellerman
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=1468284892-27765-2-git-send-email-dja@axtens.net \
--to=dja@axtens.net \
--cc=arnd@arndb.de \
--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).