From: Jason Cooper <jason@lakedaemon.net>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <marc.zyngier@arm.com>,
Barry Song <baohua@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] irqchip/sirfsoc: fix sparse warnings on __iomem
Date: Mon, 13 Jun 2016 00:52:36 +0000 [thread overview]
Message-ID: <20160613005236.GG24391@io.lakedaemon.net> (raw)
In-Reply-To: <1465301910-2308-1-git-send-email-ben.dooks@codethink.co.uk>
Hi Ben,
On Tue, Jun 07, 2016 at 01:18:30PM +0100, Ben Dooks wrote:
> Fix warnings from sparse about casting to __iomem from non anotated
> variable:
>
> drivers/irqchip/irq-sirfsoc.c:56:47: warning: incorrect type in initializer (different address spaces)
> drivers/irqchip/irq-sirfsoc.c:56:47: expected void [noderef] <asn:2>*base
> drivers/irqchip/irq-sirfsoc.c:56:47: got void *host_data
> drivers/irqchip/irq-sirfsoc.c:97:47: warning: incorrect type in initializer (different address spaces)
> drivers/irqchip/irq-sirfsoc.c:97:47: expected void [noderef] <asn:2>*base
> drivers/irqchip/irq-sirfsoc.c:97:47: got void *host_data
> drivers/irqchip/irq-sirfsoc.c:109:47: warning: incorrect type in initializer (different address spaces)
> drivers/irqchip/irq-sirfsoc.c:109:47: expected void [noderef] <asn:2>*base
> drivers/irqchip/irq-sirfsoc.c:109:47: got void *host_data
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> ---
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Jason Cooper <jason@lakedaemon.net>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Barry Song <baohua@kernel.org>
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
> ---
> drivers/irqchip/irq-sirfsoc.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
Applied to irqchip/misc
thx,
Jason.
prev parent reply other threads:[~2016-06-13 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 12:18 [PATCH] irqchip/sirfsoc: fix sparse warnings on __iomem Ben Dooks
2016-06-13 0:52 ` Jason Cooper [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=20160613005236.GG24391@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=baohua@kernel.org \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
/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