Hi James, I don't know if you haven been working on pulling this patch set into scsi-misc. If not, we would like to recall it. We understand that it doesn't conform to upstream patch submission standard, and we want to fix it. As you advised, we will make sure each patch is specific to one logic change in the resubmission. We are also working on to cleanup the bfa driver. Our first effort is reducing the number of source files, and the goal is to reduce the file number to be on a par with most upstream drivers. I will resubmit 2.1.2.1 fix first, followed by driver cleanups starting with file number reduction. Please let me know if this plan works for you. Thanks Jing > -----Original Message----- > From: James Bottomley [mailto:James.Bottomley@xxxxxxx] > Sent: Thursday, December 17, 2009 4:11 PM > To: Jing Huang > Cc: linux-scsi@xxxxxxxxxxxxxxx; Adapter Linux Open SRC Team > Subject: RE: [PATCH 0/8] bfa: update bfa driver to version 2.1.2.1 > (resubmit) > > On Wed, 2009-12-16 at 19:55 -0800, Jing Huang wrote: > > What is the status of this patch set? Is there anything I can do in > > order to get it accepted in 2.6.33 merger window? > > So, what actually happened is that it was submitted the day before the > merge window opened, so I started to reply and then got swamped with > merge window stabilisation work. > > The reply was basically that the current split up still wasn't > acceptable. What I want to see is one well described patch per logical > change. What you actually did was split them up according to some > arbitrary standard, so we got changes described as > > bfa: bfa changes part 1 > > and > > bfa: bfa changes part 2 > > So what I can do this once is accumulate all the change logs (which were > better than the first time around) and do a single update for 2.6.33 on > promise of better change sets in future. > > Is that OK? > > James > -- 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
