All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org, kay.sievers@vrfy.org,
	benh@kernel.crashing.org
Subject: Re: [RFC] driver-core: Add device node pointer to struct device
Date: Wed, 24 Feb 2010 14:36:45 -0800	[thread overview]
Message-ID: <20100224223645.GA18883@suse.de> (raw)
In-Reply-To: <fa686aa41002241409x4bcdabfet43e410eb8c480166@mail.gmail.com>

On Wed, Feb 24, 2010 at 03:09:24PM -0700, Grant Likely wrote:
> On Wed, Feb 24, 2010 at 2:44 PM, Greg KH <gregkh@suse.de> 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.

Ok, you can leave it as-is, that's not a problem.  As long as we don't
have to #ifdef the core code, it should be fine.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@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 14:36:45 -0800	[thread overview]
Message-ID: <20100224223645.GA18883@suse.de> (raw)
In-Reply-To: <fa686aa41002241409x4bcdabfet43e410eb8c480166-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed, Feb 24, 2010 at 03:09:24PM -0700, Grant Likely wrote:
> 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.

Ok, you can leave it as-is, that's not a problem.  As long as we don't
have to #ifdef the core code, it should be fine.

thanks,

greg k-h

  reply	other threads:[~2010-02-24 22:38 UTC|newest]

Thread overview: 7+ 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:10 ` Grant Likely
2010-02-24 21:44 ` Greg KH
2010-02-24 22:09   ` Grant Likely
2010-02-24 22:09     ` Grant Likely
2010-02-24 22:36     ` Greg KH [this message]
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=20100224223645.GA18883@suse.de \
    --to=gregkh@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=kay.sievers@vrfy.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.