> > Sorry about the terse description. This patch set basically updates > > the current driver in scsi-misc-2.6 to our recently released 2.1 > > driver. We couldn't make it in upstream in our initial submission > > since it was not ready at that time. Except for the second item (2 > > fixes received from upstream, which you already added into rc fix tree > > but not in scsi-misc-2.6), the remaining changes come from our > > internal 2.1 GA driver which is intended to be included in 2.6.33 > > merge window. I divide them into 7 patches for the consideration of > > patch size. Moving forward, we will make incremental changes instead > > of big patches like this. > > OK, so the fixes already in rc-fixes (and now upstream) can't go > separately into scsi-misc as part of other patches otherwise we'll get a > nasty merge conflict in linux-next (and later linus' tree at the merge > window) since rc-fixes is already upstream. > This makes sense. I will not include them in my resubmission. > So base the patch off a combination of linus' upstream tree and > scsi-misc (just pull one tree into another) and I'll sort out the > prerequisites on this end (just mention it needs patches in linus and > not in scsi-misc). > Will do this to create the patch for resubmission. > If you could do it, the enterprise distributions would very much > appreciate code clean up separated from bug fixes ... with a nice > description of the bugs actually fixed so they know what to do if bugs > come in to them. > > James > I will come up a detailed description of the issues we fixed in 2.1 driver and resubmit. Thanks Jing -- 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
