From: Grant Likely <grant.likely@secretlab.ca>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: 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>,
Greg Kroah-Hartman <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH] drivercore: Output common devicetree information in uevent
Date: Wed, 1 Feb 2012 14:29:35 -0700 [thread overview]
Message-ID: <CACxGe6uafURnPOGRNpKKXXMM06JHFoqDVqHojQdv_aeCAd_Sfg@mail.gmail.com> (raw)
In-Reply-To: <1328130989.28487.83.camel@pasglop>
On Wed, Feb 1, 2012 at 2:16 PM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> On Wed, 2012-02-01 at 11:31 -0700, Grant Likely wrote:
>> 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.
>>
>> Boot tested on ARM and compile tested on PowerPC and SPARC.
>>
>>
> We also want to generalize adding the devspec property that we have on
> PCI to all devices no ?
The pci_show_devspec() function? Yeah, that can be generalized, but
haven't researched where the best place to hook it in should be.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next parent reply other threads:[~2012-02-01 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2012-02-01 23:20 ` [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
2012-02-01 21:26 ` 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=CACxGe6uafURnPOGRNpKKXXMM06JHFoqDVqHojQdv_aeCAd_Sfg@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--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=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).