From: Greg Kroah-Hartman <greg@kroah.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
Tobias Klauser <tklauser@distanz.ch>,
Frederic Lambert <frdrc66@gmail.com>,
Rob Herring <rob.herring@calxeda.com>,
Mark Brown <broonie@sirena.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] drivercore: Output common devicetree information in uevent
Date: Wed, 1 Feb 2012 11:09:40 -0800 [thread overview]
Message-ID: <20120201190940.GC20358@kroah.com> (raw)
In-Reply-To: <1328121545-21955-1-git-send-email-grant.likely@secretlab.ca>
On Wed, Feb 01, 2012 at 11:39:04AM -0700, Grant Likely wrote:
> When userspace needs to find a specific device, it currently isn't easy to
> resolve a /sys/devices/ path from a specific device tree node. Nor is it
> easy to obtain the compatible list for devices.
>
> This patch generalizes the code that inserts OF_* values into the uevent
> device attribute so that any device that is attached to an OF node will
> have that information exported to userspace. Without this patch only
> platform devices and some powerpc-specific busses have access to this
> data.
>
> The original function also creates a MODALIAS property for the compatible
> list, but that code has not been generalized into the common case because
> it has the potential to break module loading on a lot of bus types. Bus
> types are still responsible for their own MODALIAS properties.
So you are only adding new properties to be exported, not removing any
from any existing devices, right?
If so, I have no objection to this at all, if you want to take this
through your tree for 3.4, please feel free to add:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Or I can take it through my driver-core tree, which ever is easiest for
you.
thanks,
greg k-h
next prev parent reply other threads:[~2012-02-01 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 18:39 [PATCH] drivercore: Output common devicetree information in uevent Grant Likely
2012-02-01 18:39 ` Grant Likely
2012-02-01 19:09 ` Greg Kroah-Hartman [this message]
[not found] ` <20120201190940.GC20358-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-02-01 21:26 ` Grant Likely
2012-02-01 21:26 ` Grant Likely
[not found] <1328121082-21802-1-git-send-email-grant.likely@secretlab.ca>
[not found] ` <1328130989.28487.83.camel@pasglop>
2012-02-01 21:29 ` Grant Likely
[not found] ` <CACxGe6uafURnPOGRNpKKXXMM06JHFoqDVqHojQdv_aeCAd_Sfg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-01 23:20 ` Grant Likely
2012-02-01 23:20 ` Grant Likely
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=20120201190940.GC20358@kroah.com \
--to=greg@kroah.com \
--cc=benh@kernel.crashing.org \
--cc=broonie@sirena.org.uk \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=frdrc66@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=tklauser@distanz.ch \
/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.