From: "Kashyap, Desai" <kashyap.desai@lsi.com>
To: linux-scsi@vger.kernel.org
Cc: James.Bottomley@HansenPartnership.com, Eric.Moore@lsi.com,
Sathya.Prakash@lsi.com
Subject: [PATCH 0/6] mptsas : Discription patch
Date: Wed, 2 Sep 2009 11:42:22 +0530 [thread overview]
Message-ID: <20090902061212.GA20211@lsi.com> (raw)
Discription patch
Patches are based on 2.6.31-rc8.
Patch 1,2 and 3 needs to go into stable kernel also.
Please consider this patch set for next kernel update.
[PATCH 1/6] mptsas : Sanity check for phyinfo is added.
[PATCH 2/6] mptsas : NULL pointer on big endian systems causing Expander
not to tear off
[PATCH 3/6] mptsas : PAE Kernel more than 4 GB kernel panic
[PATCH 4/6] mptsas : Send DID_NO_CONNECT for pending IOs of removed dev
[PATCH 5/6] mptsas : FW event thread and scsi mid layer deadlock in
SYNCHRONIZE CACHE command
[PATCH 6/6] mptsas : Bump version to 3.04.12
Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
---
reply other threads:[~2009-09-02 6:34 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=20090902061212.GA20211@lsi.com \
--to=kashyap.desai@lsi.com \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Sathya.Prakash@lsi.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;
as well as URLs for NNTP newsgroup(s).