linux-kernel - Re: [GIT PULL] UWB and WUSB fixes

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: <20090216160933.GA5008@kroah.com>
Date:	Mon, 16 Feb 2009 08:09:33 -0800
From:	Greg KH <greg@...ah.com>
To:	David Vrabel <david.vrabel@....com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] UWB and WUSB fixes

On Mon, Feb 16, 2009 at 02:57:54PM +0000, David Vrabel wrote:
> Greg KH wrote:
> > 
> > Also, it would be good to have the linux-usb developers at least review
> > any changes to these files, myself included, right?
> 
> I'll post patches to the list if I think they're significant enough to
> need a review.

They should all be posted to the linux-usb list please.

> > It shouldn't be any more work for you, just send the patches to me and
> > forget about them, I'll queue them up at the proper time :)
> 
> To be honest, in the past you have been too slow to handle patches and
> review in a timely manner.  The current system of sending pull request
> direct to Linus has worked well so I'm going to stick with it for now.

Things were slow when we were handling a 30+ patchset full of the whole
wusb system.  Smaller patches get handled within a week, and I've not
had any complaints about that in a while (musb withstanding, but that's
a total mess for other reasons...)

So again, I'd really like at least the ability to review the patches,
which in your current development flow, isn't even possible.

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/