From: David Miller <davem@davemloft.net>
To: grant.likely@secretlab.ca
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uartlite: Fix build on sparc.
Date: Wed, 03 Mar 2010 08:48:11 -0800 (PST) [thread overview]
Message-ID: <20100303.084811.228955847.davem@davemloft.net> (raw)
In-Reply-To: <fa686aa41003030840u45021b53y639464a7e831a63d@mail.gmail.com>
From: Grant Likely <grant.likely@secretlab.ca>
Date: Wed, 3 Mar 2010 09:40:14 -0700
> On Wed, Mar 3, 2010 at 9:04 AM, David Miller <davem@davemloft.net> wrote:
>> From: Grant Likely <grant.likely@secretlab.ca>
>> Date: Wed, 3 Mar 2010 08:51:27 -0700
>>
>>> Or if you prefer, I could expedite my patch that moves
>>> of_address_to_resource() into common code (it's currently in my test
>>> branch). I wasn't planning to merge it until 2.6.35, but it is pretty
>>> low risk so I'd be comfortable merging it now.
>>
>> I prefer if you deal with it this way.
>
> Hmmm... on second look my patch depends on a bunch of other stuff that
> doesn't work with sparc yet. grumble. Sorry, this isn't going to
> work yet. I'll have to block out the uartlite driver instead. In the
> mean time I'll change the Kconfig to omit uartlite on sparc.
BTW, while looking at this I can provide something similar to the
of_address_to_resource() interface on sparc but it would need
to provide the of_device pointer not the device_node one.
I precompute all of the IRQs and I/O addresses of OF nodes and stick
them into of_device->resource[] and of_device->irq[].
So if I have the of_device pointer I can just:
memset(res, op->resource[n], sizeof(*res));
as my implementation.
next prev parent reply other threads:[~2010-03-03 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 10:50 [PATCH] uartlite: Fix build on sparc David Miller
2010-03-03 15:51 ` Grant Likely
2010-03-03 16:04 ` David Miller
2010-03-03 16:40 ` Grant Likely
2010-03-03 16:44 ` Grant Likely
2010-03-03 16:48 ` David Miller [this message]
2010-03-03 18:52 ` Grant Likely
2010-03-03 18:55 ` Grant Likely
2010-03-04 2:50 ` Greg KH
2010-03-04 4:34 ` Greg KH
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=20100303.084811.228955847.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.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