From: James Bottomley <James.Bottomley@suse.de>
To: "Kashyap, Desai" <kashyap.desai@lsi.com>
Cc: linux-scsi@vger.kernel.org, Eric.Moore@lsi.com, Sathya.Prakash@lsi.com
Subject: Re: [PATCH 0/10] mpt2sas: Description Patch
Date: Tue, 04 Jan 2011 10:00:48 -0600 [thread overview]
Message-ID: <1294156848.4726.8.camel@mulgrave.site> (raw)
In-Reply-To: <20110104060032.GA5751@lsi.com>
On Tue, 2011-01-04 at 11:30 +0530, Kashyap, Desai wrote:
> MPT2SAS driver changes.
> These patches are taken from 2.6.37-rc5.
> Please consider this patch set for next kernel release.
That's a bit unlikely considering we're probably only a day or so away
from a 2.6.37 kernel release. It takes time to go through the
linux-next and code inspection process.
I can add them to scsi-misc with a cc stable (at least for the ones that
are bug fixes):
> [PATCH 01/10] mpt2sas: Device removal handshake even though the
> PHYSTATUS_VACANT bit is set in the PhyStatus
> [PATCH 02/10] mpt2sas: Internal device reset complete event is not
> supported for older firmware prior to MPI Rev K
> [PATCH 03/10] mpt2sas: Correct resizing calculation for max_queue_depth
> [PATCH 04/10] mpt2sas: Revision P MPI Header Update
This is an update not a bug fix
> [PATCH 05/10] mpt2sas: Add support for Customer specific branding messages
This is an update, not a bug fix
> [PATCH 06/10] mpt2sas: Fix the race between broadcast asyn event and scsi
> command completion.
This patch seems to contain half the branding stuff from 5/10 ... please
separate them
> [PATCH 07/10] mpt2sas: Prevent access to freed memory from port enable process
> [PATCH 08/10] mpt2sas: Basic Code Cleanup in mpt2sas_base
A code cleanup is not a bug fix.
> [PATCH 09/10] mpt2sas: Call the _scsih_ir_shutdown prior to reporting the
> volumes missing from the OS
> [PATCH 10/10] mpt2sas: Bump version 08.100.00.00
>
> Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
So that's 1-3 bug fixes, rework 5,6 so it becomes a clean separation
between enhancement and bug fix and 7,9 are bug fixes.
James
next prev parent reply other threads:[~2011-01-04 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 6:00 [PATCH 0/10] mpt2sas: Description Patch Kashyap, Desai
2011-01-04 16:00 ` James Bottomley [this message]
2011-01-04 19:33 ` Desai, Kashyap
2011-01-18 18:29 ` Desai, Kashyap
-- strict thread matches above, loose matches on Subject: below --
2009-12-16 13:17 [PATCH 0/10] mpt2sas : description patch Kashyap, Desai
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=1294156848.4726.8.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=Eric.Moore@lsi.com \
--cc=Sathya.Prakash@lsi.com \
--cc=kashyap.desai@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