From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH v2 1/1] x86/early_printk: Use __iomem address space for IO
Date: Fri, 09 Oct 2015 17:35:12 +0300 [thread overview]
Message-ID: <1444401312.8361.547.camel@linux.intel.com> (raw)
In-Reply-To: <1444400949-103551-1-git-send-email-andriy.shevchenko@linux.intel.com>
On Fri, 2015-10-09 at 17:29 +0300, Andy Shevchenko wrote:
> There are following warnings on unpatched code:
>
> arch/x86/kernel/early_printk.c:198:32: warning: incorrect type in
> initializer (different address spaces)
> arch/x86/kernel/early_printk.c:198:32: expected void [noderef]
> <asn:2>*vaddr
> arch/x86/kernel/early_printk.c:198:32: got unsigned int [usertype]
> *<noident>
> arch/x86/kernel/early_printk.c:205:32: warning: incorrect type in
> initializer (different address spaces)
> arch/x86/kernel/early_printk.c:205:32: expected void [noderef]
> <asn:2>*vaddr
> arch/x86/kernel/early_printk.c:205:32: got unsigned int [usertype]
> *<noident>
This one is wrong, sorry for noise.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> v2:
> - amend subject line
> arch/x86/kernel/early_printk.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/early_printk.c
> b/arch/x86/kernel/early_printk.c
> index 076a4a7..77f2f5c 100644
> --- a/arch/x86/kernel/early_printk.c
> +++ b/arch/x86/kernel/early_printk.c
> @@ -195,14 +195,14 @@ static __init void early_serial_init(char *s)
> #ifdef CONFIG_PCI
> static void mem32_serial_out(unsigned long addr, int offset, int
> value)
> {
> - u32 *vaddr = (u32 *)addr;
> + void __iomem *vaddr = (void __iomem *)addr;
> /* shift implied by pointer type */
> writel(value, vaddr + offset);
> }
>
> static unsigned int mem32_serial_in(unsigned long addr, int offset)
> {
> - u32 *vaddr = (u32 *)addr;
> + void __iomem *vaddr = (void __iomem *)addr;
> /* shift implied by pointer type */
> return readl(vaddr + offset);
> }
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2015-10-09 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 14:29 Andy Shevchenko
2015-10-09 14:35 ` Andy Shevchenko [this message]
2015-10-11 19:18 ` Thomas Gleixner
2015-10-12 8:12 ` Andy Shevchenko
2015-10-12 9:11 ` Thomas Gleixner
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=1444401312.8361.547.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
Powered by JetHome