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] mpt fusion: Firmware Event implementation using seperate WorkQueue
Date: Fri, 3 Apr 2009 17:16:44 +0530 [thread overview]
Message-ID: <20090403114626.GA17721@lsi.com> (raw)
These patches are created on top of MPT fusion previous patch applied on
date 26/02/2009 with subject line: "mpt fusion: config, Taskmgmt cmd,
Internal cmd, Ioctl cmd changes"
Some patches are splited into two diffrent patches only for readability
purpose for reviewer.
Consider below patches as one logical patch. There is no harm to send
those patches as single patch, but to give more readability I have choosen
to split.
PATCH 2 and PATCH 3.
PATCH 4 and PATCH 5.
PATCH 3 and PATCH 5 include only those function which are not part of MPT
fusion.
---
Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
---
next reply other threads:[~2009-04-03 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 11:46 Kashyap, Desai [this message]
2009-04-03 20:44 ` [PATCH 0/6] mpt fusion: Firmware Event implementation using seperate WorkQueue James Bottomley
2009-04-06 5:09 ` Desai, Kashyap
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=20090403114626.GA17721@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