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: <CACxGe6semcPXkGfEN76DezbC-sAgkczjofbjvbexM8g_8gPdBw@mail.gmail.com>
Date:	Wed, 1 Feb 2012 14:26:14 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Greg Kroah-Hartman <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
	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>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: [PATCH] drivercore: Output common devicetree information in uevent

On Wed, Feb 1, 2012 at 12:09 PM, Greg Kroah-Hartman <greg@...ah.com> wrote:
> 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@...uxfoundation.org>
>
> Or I can take it through my driver-core tree, which ever is easiest for
> you.

I'll take it via the devicetree branch.  Thanks.

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/