From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Subject: Re: [PATCH] drivercore: Output common devicetree information in uevent Date: Wed, 1 Feb 2012 11:09:40 -0800 Message-ID: <20120201190940.GC20358@kroah.com> References: <1328121545-21955-1-git-send-email-grant.likely@secretlab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1328121545-21955-1-git-send-email-grant.likely@secretlab.ca> Sender: linux-kernel-owner@vger.kernel.org To: Grant Likely Cc: linux-kernel@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, Tobias Klauser , Frederic Lambert , Rob Herring , Mark Brown , "David S. Miller" , Benjamin Herrenschmidt List-Id: devicetree@vger.kernel.org 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 Or I can take it through my driver-core tree, which ever is easiest for you. thanks, greg k-h