All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: torvalds@transmeta.com, linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] USB changes for 2.5.66
Date: Wed, 26 Mar 2003 10:35:14 -0800	[thread overview]
Message-ID: <20030326183514.GD24689@kroah.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1030326131317.8110E-100000@gatekeeper.tmr.com>

On Wed, Mar 26, 2003 at 01:17:56PM -0500, Bill Davidsen wrote:
> On Tue, 25 Mar 2003, Greg KH wrote:
> 
> > Hi,
> > 
> > Here are some small USB changes.  Basically all little cleanups and
> > bugfixes, nothing major.
> > 
> > Please pull from:  bk://linuxusb.bkbits.net/linus-2.5
> 
> Another "bk-only" patch. Guess I'd better look at the free (as in license,
> not cost) clone again.

Not true at all (as I've stated many times in the past...)

The USB patches that I send to Linus through BK are all sent to the
linux-usb-devel mailing list as followups to this message.

They are also placed at kernel.org in:
	/pub/linux/kernel/people/gregkh/usb/2.5/*.2.5.66*

So no, I always provide patches, I just don't flood lkml with USB
specific ones.

thanks,

greg k-h

  parent reply	other threads:[~2003-03-26 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26  0:54 [BK PATCH] USB changes for 2.5.66 Greg KH
2003-03-26 18:17 ` Bill Davidsen
2003-03-26 18:34   ` Linus Torvalds
2003-03-26 20:22     ` [linux-usb-devel] " Alan Cox
2003-03-26 20:42       ` Thomas Molina
2003-03-27 22:48     ` Bill Davidsen
2003-03-29 14:33     ` John Goerzen
2003-03-26 18:35   ` Greg KH [this message]
2003-03-26 20:02   ` Alan Cox

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=20030326183514.GD24689@kroah.com \
    --to=greg@kroah.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=torvalds@transmeta.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.