From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] locomo.c: make irq register access typesafe
Date: Thu, 21 Jan 2010 10:41:46 +0800 [thread overview]
Message-ID: <f17812d71001201841w34abc3b5w49b8c2986897dbe8@mail.gmail.com> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909020E8E46@mi8nycmail19.Mi8.com>
On Thu, Jan 21, 2010 at 10:31 AM, H Hartley Sweeten
<hartleys@visionengravers.com> wrote:
> On Wednesday, January 20, 2010 7:13 PM, Eric Miao wrote:
>> On Thu, Jan 21, 2010 at 2:10 AM, H Hartley Sweeten
>> <hartleys@visionengravers.com> wrote:
>>> In locomo_setup_irq a void __iomem * is stored by set_irq_chip_data
>>> to hold the base address for the irq registers. ?Unfortunately chip_data
>>> is a void *. This will cause a number of (different address space) sparse
>>> warnings.
>>>
>>
>> That's actually been fixed as a side effect in my previous proposed
>> irq cleanup patches. The way is to pass locomo chip as the data
>> instead of a raw pointer. Please let me know how you think, the
>> specific patch follows:
>
> There must be some other patches to locomo.c that remove the locomo_key_*,
> locomo_gpio_*, locomo_lt_*, and locomo_spi_* related stuff. ?Were all of
> them merged into common code? ?Where can I find a reference to the
> original patches?
>
Cannot find the reference atm but they were posted weeks ago.
> Other than that it looks good to me.
Thanks.
next prev parent reply other threads:[~2010-01-21 2:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 18:10 [PATCH] locomo.c: make irq register access typesafe H Hartley Sweeten
2010-01-21 2:13 ` Eric Miao
2010-01-21 2:31 ` H Hartley Sweeten
2010-01-21 2:41 ` Eric Miao [this message]
2010-01-21 2:59 ` H Hartley Sweeten
2010-03-08 23:22 ` H Hartley Sweeten
2010-03-08 23:46 ` Russell King - ARM Linux
2010-03-08 23:56 ` H Hartley Sweeten
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=f17812d71001201841w34abc3b5w49b8c2986897dbe8@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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