From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
kay.sievers-tD+1rO4QERM@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC] driver-core: Add device node pointer to struct device
Date: Wed, 24 Feb 2010 15:09:24 -0700 [thread overview]
Message-ID: <fa686aa41002241409x4bcdabfet43e410eb8c480166@mail.gmail.com> (raw)
In-Reply-To: <20100224214442.GB18437-l3A5Bk7waGM@public.gmane.org>
On Wed, Feb 24, 2010 at 2:44 PM, Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org> wrote:
> On Wed, Feb 24, 2010 at 02:10:30PM -0700, Grant Likely wrote:
>> Greg and Kay,
>>
>> This is a patch from a larger series of OF related cleanup patches. This
>> one adds a new 'of_node' member to struct device, conditional upon
>> CONFIG_OF. The goal is to move of_node out of archdata because all
>> arches using CONFIG_OF need it.
>>
>> Before I commit too much effort down this path, I want to get your
>> feedback. Do you have any objections to this change to struct device?
>>
>> @@ -414,6 +415,9 @@ struct device {
>> override */
>> /* arch specific additions */
>> struct dev_archdata archdata;
>> +#ifdef CONFIG_OF
>> + struct device_node *of_node;
>> +#endif
>
> No objection from me, but do we really need the #ifdef here?
I added the #ifdef because it is complete dead weight when CONFIG_OF
is not set. However, I'll defer to your preference here on what looks
cleaner w.r.t. maintenance.
>> Full patch follows...
>
> Do you want to take this patch through your tree? If so, feel free to
> add:
> Acked-by: Greg Kroah-Hartman <gregkh-l3A5Bk7waGM@public.gmane.org>
I'll take it through my tree. I've got a lot of related patches that
it should be grouped with, and I'm going to defer it to the 2.6.35
merge window so that it can get some linux-next exposure.
> to the patch.
>
> If not, let me know and I'll take it through my tree.
>
> Glad to see this work coming along, nice job.
Thanks!
Cheers,
g.
next prev parent reply other threads:[~2010-02-24 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 21:10 [RFC] driver-core: Add device node pointer to struct device Grant Likely
2010-02-24 21:44 ` Greg KH
[not found] ` <20100224214442.GB18437-l3A5Bk7waGM@public.gmane.org>
2010-02-24 22:09 ` Grant Likely [this message]
[not found] ` <fa686aa41002241409x4bcdabfet43e410eb8c480166-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-24 22:36 ` 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=fa686aa41002241409x4bcdabfet43e410eb8c480166@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=gregkh-l3A5Bk7waGM@public.gmane.org \
--cc=kay.sievers-tD+1rO4QERM@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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