public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Gal Rosen <galr@storwize.com>
To: James Smart <james.smart@emulex.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] SCSI: Synchronization issue while deleting vport
Date: Mon, 08 Mar 2010 10:05:25 +0200	[thread overview]
Message-ID: <1268035525.2229.12.camel@galr-linux> (raw)
In-Reply-To: <4B5DBA51.9070500@emulex.com>

Hello James,

Do you know why the patch still not included even in scsi-rc-fixes-2.6 ?

Can you push it ?

Thanks,
Gal.

On Mon, 2010-01-25 at 10:35 -0500, James Smart wrote:
> James B controls the merge into upstream.  He will most likely include the 
> patch in scsi-rc-fixes-2.6, which will merge into one of the 2.6.33-rc? phases.
> 
> I assume the process, to get it into an already released kernel rev, is to 
> petition the 2.6.<rev>-stable tree maintainer (usually GregKH) to pick it up. 
>   You do need to be careful, as some changes are dependent on other things 
> that may have changed since that kernel revision. However, I don't think this 
> change would have that problem.
> 
> -- james s
> 
> 
> 
> Gal Rosen wrote:
> > James,
> > 
> > What is the process until it will enter to the code ?
> > and for what version 2.6.26 or 2.6.33 ?
> > 
> > Thanks,
> > Gal.
> > On Fri, 2010-01-22 at 21:00 -0500, James Smart wrote:
> >> Gal,
> >>
> >> Thanks for correcting this issue.  Patch looks good.
> >>
> >> Signed-off-by: James Smart <james.smart@emulex.com>
> >>
> >>
> >>
> >> Gal Rosen wrote:
> >>> Hi,
> >>>
> >>> Attach proposed patch for the PROBLEM: Synchronization issue in
> >>> scsi_transport_fc.
> >>>
> >>> Gal Rosen.
> >>>
> > 


  reply	other threads:[~2010-03-08  8:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21  8:15 [PATCH] SCSI: Synchronization issue while deleting vport Gal Rosen
2010-01-23  2:00 ` James Smart
2010-01-24  7:20   ` Gal Rosen
2010-01-25 15:35     ` James Smart
2010-03-08  8:05       ` Gal Rosen [this message]
2010-03-08 16:42         ` James Smart
2010-03-08 17:12 ` James Bottomley

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=1268035525.2229.12.camel@galr-linux \
    --to=galr@storwize.com \
    --cc=james.smart@emulex.com \
    --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