From: James Bottomley <James.Bottomley@suse.de>
To: Jim Schutt <jaschut@sandia.gov>
Cc: linux-kernel@vger.kernel.org, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: 2.6.39-rc5+ BUG at scsi_run_queue+0x24/0xe3
Date: Tue, 03 May 2011 15:36:25 -0500 [thread overview]
Message-ID: <1304454985.14015.3.camel@mulgrave.site> (raw)
In-Reply-To: <4DC04EF0.4020909@sandia.gov>
On Tue, 2011-05-03 at 12:52 -0600, Jim Schutt wrote:
> FWIW, I noticed that commit 99f3c722e23 in scsi-rc-fixes-2.6
> might want a Cc: stable@kernel.org, since the commit it's
> fixing, 86cbfb5607d4, had one.
>
> I'm not sure how that all works, but I thought I'd mention it
> just in case.
Yes, good point; I'll add it ... destabilising the stable kernels
wouldn't be a very good idea.
James
prev parent reply other threads:[~2011-05-03 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DC0330F.6050906@sandia.gov>
[not found] ` <1304442019.10982.7.camel@mulgrave.site>
[not found] ` <4DC03B0A.50209@sandia.gov>
2011-05-03 17:37 ` 2.6.39-rc5+ BUG at scsi_run_queue+0x24/0xe3 James Bottomley
2011-05-03 17:54 ` Jim Schutt
2011-05-03 18:52 ` Jim Schutt
2011-05-03 20:36 ` James Bottomley [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=1304454985.14015.3.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=jaschut@sandia.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).