From: James Smart <James.Smart@Emulex.Com>
To: James Bottomley <James.Bottomley@SteelEye.com>,
linux-scsi <linux-scsi@vger.kernel.org>, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@osdl.org>
Subject: Missing Patches - please pull these in....
Date: Mon, 26 Jun 2006 17:07:25 -0400 [thread overview]
Message-ID: <44A04C8D.3070008@emulex.com> (raw)
James,
I looked at your 2.6.17 drop as well as the latest scsi-misc-2.6 tree,
and the following patches have not yet been applied. Can you please
do so as soon as possible (especially on the one posted in March).
-- james s
3/8/06: [PATCH Repost 0/2] Block I/O while SG reset operation in progress
http://marc.theaimsgroup.com/?l=linux-scsi&m=114184745819730&w=2
http://marc.theaimsgroup.com/?l=linux-scsi&m=114184745830216&w=2
http://marc.theaimsgroup.com/?l=linux-scsi&m=114184745819007&w=2
5/11/06: [PATCH] fc transport: resolve scan vs delete deadlocks (CRITICAL)
http://marc.theaimsgroup.com/?l=linux-scsi&m=114736846214310&w=2
5/16/06: [REPOST #2][PATCH] update max sdev block limit
http://marc.theaimsgroup.com/?l=linux-scsi&m=114781033210150&w=2
6/15/06: [PATCH] scsi_scan.c: bug fix: starget use after free issue (CRITICAL)
http://marc.theaimsgroup.com/?l=linux-scsi&m=115039057504409&w=2
And these new ones are critical as well:
6/26/06: [REPOST][PATCH] fc transport: bug fix: correct references (CRITICAL)
http://marc.theaimsgroup.com/?l=linux-scsi&m=115134614426385&w=2
6/26/06: [PATCH] scsi midlayer: fix sdev reuse after free (CRITICAL)
http://marc.theaimsgroup.com/?l=linux-scsi&m=115134812215106&w=2
reply other threads:[~2006-06-26 21:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44A04C8D.3070008@emulex.com \
--to=james.smart@emulex.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.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 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.