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@xxxxxxxxxx>
Gal Rosen wrote:
Hi,
Attach proposed patch for the PROBLEM: Synchronization issue in
scsi_transport_fc.
Gal Rosen.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
