linux-kernel - Re: [PATCH] drivercore: Output common devicetree information in uevent

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACxGe6vU=jL7tqXQKdzqksEmDNgvN5U+HdypgC3bUcQaqxSuRQ@mail.gmail.com>
Date:	Wed, 1 Feb 2012 16:20:57 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Tobias Klauser <tklauser@...tanz.ch>,
	Frederic Lambert <frdrc66@...il.com>,
	Rob Herring <rob.herring@...xeda.com>,
	Mark Brown <broonie@...ena.org.uk>,
	"David S. Miller" <davem@...emloft.net>,
	Greg Kroah-Hartman <greg@...ah.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	devicetree-discuss <devicetree-discuss@...ts.ozlabs.org>
Subject: Re: [PATCH] drivercore: Output common devicetree information in uevent

On Wed, Feb 1, 2012 at 2:29 PM, Grant Likely <grant.likely@...retlab.ca> wrote:
> On Wed, Feb 1, 2012 at 2:16 PM, Benjamin Herrenschmidt
> <benh@...nel.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.

Is there any point in generalizing that attribute though when the data
is in uevent?

g.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/