All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Duncan Sands <baldrick@free.fr>
Cc: Grzegorz Kulewski <kangur@polcom.net>,
	linux-kernel@vger.kernel.org, torvalds@osdl.org,
	linux-usb-devel@lists.sourceforge.net, speedtouch@ml.free.fr
Subject: Re: [linux-usb-devel] 3 USB regressions (2.6.6-rc3-bk1) that should be fixed before 2.6.6
Date: Fri, 30 Apr 2004 08:55:21 -0700	[thread overview]
Message-ID: <20040430155521.GA4463@kroah.com> (raw)
In-Reply-To: <200404300952.00454.baldrick@free.fr>

On Fri, Apr 30, 2004 at 09:52:00AM +0200, Duncan Sands wrote:
> (1) get Greg's latest bitkeeper tree (bk://kernel.bkbits.net/gregkh/linux/usb-2.6)

Or if you don't like using bitkeeper, use the latest -mm release.  All
of the changes in my tree are in there.

Honestly, I don't see how some of these issues started showing up
between those two kernel releases.  You can see the only changes made in
the USB section broken out by patch at:
	kernel.org/pub/linux/kernel/people/gregkh/2.6/2.6.6-rc2/

If you want, try reversing those patches one by one against 2.6.6-rc3 to
see which one caused the problems.

thanks,

greg k-h

  reply	other threads:[~2004-04-30 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 23:32 3 USB regressions (2.6.6-rc3-bk1) that should be fixed before 2.6.6 Grzegorz Kulewski
2004-04-29 23:35 ` Grzegorz Kulewski
2004-04-30  7:52 ` [linux-usb-devel] " Duncan Sands
2004-04-30 15:55   ` Greg KH [this message]
2004-04-30 16:10     ` Duncan Sands
2004-04-30 22:41       ` Greg KH
2004-05-02 20:53         ` Duncan Sands
2004-05-07 23:24           ` Greg KH

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=20040430155521.GA4463@kroah.com \
    --to=greg@kroah.com \
    --cc=baldrick@free.fr \
    --cc=kangur@polcom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=speedtouch@ml.free.fr \
    --cc=torvalds@osdl.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 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.