linux-kernel - Re: [PATCH 01/20] drivers_base: platform: use always ->name for 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110823153243.GB25968@suse.de>
Date:	Tue, 23 Aug 2011 08:32:43 -0700
From:	Greg KH <gregkh@...e.de>
To:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	linux-usb@...r.kernel.org, Felipe Balbi <balbi@...com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/20] drivers_base: platform: use always ->name for
 uevent

On Tue, Aug 23, 2011 at 11:50:36AM +0200, Sebastian Andrzej Siewior wrote:
> * Greg KH | 2011-08-22 14:51:51 [-0700]:
> 
> >> Greg, do you want to take this patch through your driver core tree, or
> >> would you prefer to have it come through the xHCI tree?
> >
> >I'll take it in my driver-core tree separate, as the others don't depend
> >on this one, right?
> 
> Should the xhci series hit Linus' tree before your driver-core than
> rmmod of the xhci-pci driver will lead to a crash.

That's ok, just don't do that :)

And you can tell me to merge stuff with Linus after one of my other
trees is applied, I can do that as well.

greg k-h
--
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/