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, 7 May 2004 16:24:36 -0700	[thread overview]
Message-ID: <20040507232436.GN14660@kroah.com> (raw)
In-Reply-To: <200405022253.03011.baldrick@free.fr>

On Sun, May 02, 2004 at 10:53:03PM +0200, Duncan Sands wrote:
> > > Hi Greg, I'm not sure when these problems started showing up, maybe they
> > > have been in 2.6.6- for a while.  One patch that may be worth having in
> > > 2.6.6 by the way is the one for device_disconnect in devio.c that changes
> > > destroy_all_async to destroy_async_on_interface.  It's clearly correct
> > > and does do some good!
> >
> > Care to point out which one this was?  I'm swimming in a sea of patches
> > right now :)
> 
> I rediffed it against Linus's current tree.  The extern -> static change is to make sure
> we avoid the problem reported by R. J. Wysocki for -rc3-mm1: unknown symbol
> destroy_all_async.

Hm, at this point in time, I'll just wait on this.  2.6.6 should be out
shortly I hope...

thanks,

greg k-h

      reply	other threads:[~2004-05-08  0:25 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
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 [this message]

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=20040507232436.GN14660@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.