linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: SCSI development list <linux-scsi@vger.kernel.org>,
	Luben Tuikov <ltuikov@yahoo.com>,
	stable@kernel.org
Subject: Re: [stable] Submit commit 3dea642afd for 2.6.38.stable?
Date: Wed, 18 May 2011 17:27:27 -0700	[thread overview]
Message-ID: <20110519002727.GD8697@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1105161626070.2013-100000@iolanthe.rowland.org>

On Mon, May 16, 2011 at 04:45:15PM -0400, Alan Stern wrote:
> James:
> 
> Your commit 3dea642afd9187728d119fce5c82a7ed9faa9b6a ([SCSI] Revert
> "[SCSI] Retrieve the Caching mode page") hasn't been submitted for the
> 2.6.38 stable tree.  More people are now getting hit with the
> underlying problem; see
> 
> 	https://bugzilla.kernel.org/show_bug.cgi?id=35042
> 
> Do you want to queue your commit to the stable tree, or do you prefer
> to wait until the proper repair patch:
> 
> 	http://marc.info/?l=linux-scsi&m=130089710431684&w=2
> 
> has been merged so it can go into the stable tree instead?
> 
> Alan Stern
> 
> P.S.: As of now, the scsi-next tree doesn't show any signs of
> reinstating Luben's original commit together with my repair patch.  
> Does this mean you intend to forget about the original "Retrieve the
> Caching mode page" change, or do you intend to merge them for 2.6.41?)

James, any ideas?

thanks,

greg k-h

  reply	other threads:[~2011-05-19  0:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 20:45 Submit commit 3dea642afd for 2.6.38.stable? Alan Stern
2011-05-19  0:27 ` Greg KH [this message]
2011-05-19  4:02 ` James Bottomley
2011-05-19  6:07   ` Luben Tuikov
2011-05-19 14:19   ` Alan Stern
2011-05-19 15:28     ` 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=20110519002727.GD8697@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ltuikov@yahoo.com \
    --cc=stable@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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).