linux-kernel - Re: linux-next: manual merge of the usb-gadget tree with the driver-core tree

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: <20141118162436.GA1108@kroah.com>
Date:	Tue, 18 Nov 2014 08:24:36 -0800
From:	Greg KH <greg@...ah.com>
To:	Felipe Balbi <balbi@...com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Wolfram Sang <wsa@...-dreams.de>,
	Dinh Nguyen <dinguyen@...nsource.altera.com>,
	Paul Zimmerman <paul.zimmerman@...opsys.com>
Subject: Re: linux-next: manual merge of the usb-gadget tree with the
 driver-core tree

On Tue, Nov 18, 2014 at 09:25:31AM -0600, Felipe Balbi wrote:
> Hi,
> 
> On Tue, Nov 18, 2014 at 06:12:22PM +1100, Stephen Rothwell wrote:
> > Hi Felipe,
> > 
> > Today's linux-next merge of the usb-gadget tree got a conflict in
> > drivers/usb/dwc2/gadget.c between commit 7c3e90537b74 ("usb: dwc2: drop
> > owner assignment from platform_drivers") from the driver-core tree and
> 
> why is that commit in the driver-core tree ? It wasn't even acked by
> Paul Z. It wasn't sent to linux-usb either.
> 
> Sure, it's minimal, but I'd expect a little cordiality in Ccing driver
> maintainers ;-)

We fixed up many hundreds of drivers all at once, it was easier to take
that change through my driver-core tree than try to coordinate in
everyone's different trees and end up missing some usages.

thanks,

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/