public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Vrabel <david.vrabel@csr.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] UWB and WUSB fixes
Date: Mon, 16 Feb 2009 08:09:33 -0800	[thread overview]
Message-ID: <20090216160933.GA5008@kroah.com> (raw)
In-Reply-To: <49997EF2.4070109@csr.com>

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

  reply	other threads:[~2009-02-16 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 18:06 [GIT PULL] UWB and WUSB fixes David Vrabel
2009-02-03  5:12 ` Greg KH
2009-02-03 14:14   ` David Vrabel
2009-02-03 15:47     ` Greg KH
2009-02-16 14:57       ` David Vrabel
2009-02-16 16:09         ` Greg KH [this message]
2009-02-16 18:03           ` David Vrabel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090216160933.GA5008@kroah.com \
    --to=greg@kroah.com \
    --cc=david.vrabel@csr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox