All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Warren <SWarren@nvidia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "Oops" in 2.6.9 SCSI w/ usb-storage & multi-LUN
Date: Tue, 21 Dec 2004 09:04:03 -0800	[thread overview]
Message-ID: <20041221170403.GA1459@kroah.com> (raw)
In-Reply-To: <DBFABB80F7FD3143A911F9E6CFD477B003CE0CC2@hqemmail02.nvidia.com>

On Mon, Dec 20, 2004 at 05:23:44PM -0800, Stephen Warren wrote:
> I've tried both test application under 2.6.10-rc3, and everything seems
> to work fine on that kernel. I see there were a lot of USB changes in
> 2.6.10.

2.6.10 isn't released yet :)

> Does anyone know what change from 2.6.10 fixed this specific issue. Is
> it something that's easy to isolate and back-port to 2.6.9?

Lots of different scsi and usb changes probably helped fix this.  I
suggest just going through the different patches and trying to narrow it
down if you really need to backport this.

Good luck,

greg k-h

      reply	other threads:[~2004-12-21 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21  1:23 "Oops" in 2.6.9 SCSI w/ usb-storage & multi-LUN Stephen Warren
2004-12-21 17:04 ` 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=20041221170403.GA1459@kroah.com \
    --to=greg@kroah.com \
    --cc=SWarren@nvidia.com \
    --cc=linux-kernel@vger.kernel.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.