linux-kernel - Re: linux-next: manual merge of the usb-gadget tree with the vfs 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]

Date:	Thu, 18 Sep 2014 12:12:26 -0500
From:	Felipe Balbi <balbi@...com>
To:	Felipe Balbi <balbi@...com>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Al Viro <viro@...IV.linux.org.uk>,
	<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	Robert Baldyga <r.baldyga@...sung.com>
Subject: Re: linux-next: manual merge of the usb-gadget tree with the vfs tree

Hi,

On Wed, Sep 17, 2014 at 10:34:00AM -0500, Felipe Balbi wrote:
> On Wed, Sep 17, 2014 at 04:16:58PM +1000, Stephen Rothwell wrote:
> > Hi Felipe,
> > 
> > Today's linux-next merge of the usb-gadget tree got a conflict in
> > drivers/usb/gadget/function/f_fs.c between commit 8322215aa91c ("f_fs:
> 
> I can't find this commit on linux-usb. In fact, googling for it the only
> reference I find to that commit is this very thread. I would strong
> suggest that it be removed from the tree as it, apparently, went in
> without any review. Sure, it's a simple change, but it needs to be
> reviewed and needs to be sent to proper maintainers.
> 
> Unless I'm missing something, of course, but I could not find any other
> references to this commit.
> 
> Al, was this commit sent to any mailing list ?

a gentle ping here

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)