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: Tue, 3 Feb 2009 07:47:45 -0800 [thread overview]
Message-ID: <20090203154745.GA27533@kroah.com> (raw)
In-Reply-To: <49885139.3070106@csr.com>
On Tue, Feb 03, 2009 at 02:14:17PM +0000, David Vrabel wrote:
> Greg KH wrote:
> > On Mon, Feb 02, 2009 at 06:06:42PM +0000, David Vrabel wrote:
> >> drivers/usb/host/whci/asl.c | 9 +++++++--
> >> drivers/usb/host/whci/hw.c | 15 +++++++++++++++
> >> drivers/usb/host/whci/pzl.c | 9 +++++++--
> >> drivers/usb/host/whci/whcd.h | 1 +
> >> drivers/usb/wusbcore/devconnect.c | 1 +
> >> drivers/usb/wusbcore/rh.c | 3 +++
> >
> > For patches under drivers/usb/ could you please route them through me?
> > It makes things a bit easier to coordinate at times. Not that there is
> > a problem at all with these patches, but in the future it would be
> > nicer.
>
> This is more work for me (and you) and I don't see the benefit. Could
> you expand on what situations you see this as helping?
I carry changes to drivers/usb/host all the time that can affect whci
due to changes in the USB hcd interface. Also, people end up sending me
patches for these files for things like header file cleanups and other
minor stuff.
So that can potentially conflict with stuff you are doing without the
my knowledge.
Also, it would be good to have the linux-usb developers at least review
any changes to these files, myself included, right?
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 :)
thanks,
greg k-h
next prev parent reply other threads:[~2009-02-03 15:52 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 [this message]
2009-02-16 14:57 ` David Vrabel
2009-02-16 16:09 ` Greg KH
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=20090203154745.GA27533@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