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@xxxxxxx> > --- > -- > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
