From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Kashyap, Desai" <kashyap.desai@lsi.com>
Cc: linux-scsi@vger.kernel.org, Eric.Moore@lsi.com, Sathya.Prakash@lsi.com
Subject: Re: [PATCH 00/06] mptfusion : (Resend) Description patch
Date: Thu, 10 Feb 2011 15:05:58 +0000 [thread overview]
Message-ID: <1297350358.4933.22.camel@mulgrave.site> (raw)
In-Reply-To: <20110210061746.GA31424@lsi.com>
On Thu, 2011-02-10 at 11:47 +0530, Kashyap, Desai wrote:
> MPT Fusion driver updates. Please consider it for next rc update.
We still have a basic confusion here: Things that are enhancements or
optimisations can't go in the next rc update, they have to wait for the
merge window. What I need are two separate patch sets: one for the
fixes tree and one for the merge window. As long as the patches below
separate easily, I can do this manually (basically only 4,5 are bug
fixes) ... where do you want the version change to go? With the entire
patch set (so in the merge window)?
James
> Resending patch set. Corrected posting to stable kernel as requested by
> Greg and following correct process of posting patches to stable kernel.
>
> First three patches are New Feature/Optimization. Patch 4,5 are Fixes.
> Removed sas_address sysfs addition as commented by James from patch-1.
>
> [PATCH 01/06] mptfusion: (New Feature)Added new sysfs parameters for handle
> and haldles.
> [PATCH 02/06] mptfusion: (New Feature)Support SAS2.0 Devices with SAS1.0 Controllers
> [PATCH 03/06] mptfusion: (Optmization)Remove bus reset for mptsas module
> [PATCH 04/06] mptfusion: (Fix) mptctl_release is required in mptctl.c
> [PATCH 05/06] mptfusion: (Fix) Incorrect return value in mptscsih_dev_reset
> [PATCH 06/06] mptfusion: Bump version 03.04.18
>
> Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
> ---
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-10 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 6:17 [PATCH 00/06] mptfusion : (Resend) Description patch Kashyap, Desai
2011-02-10 15:05 ` James Bottomley [this message]
2011-02-10 16:04 ` 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=1297350358.4933.22.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--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