On Wed, 2017-02-08 at 17:06 +0000, Bart Van Assche wrote: > On Wed, 2017-02-08 at 08:54 -0800, Nicholas A. Bellinger wrote: > > I'll be sending the v4.10 series to Linus soon. > > This needs further clarification. Someone who sends pull requests to > Linus is a maintainer and hence is expected to review patches others > post for the subsystem that is being maintained and is also expected > to ask questions from users about that subsystem. The past few months > you have ignored SCSI target patches posted by others. How do you see > your own role from now on with regard to the SCSI target subsystem? > Well, I've been maintaining the target subsystem for the last 6 years in-tree, and a total of 10 years out of tree. I've always been ultimately responsible for the stability and root causing bugs for the community. Not a trival thing.. Because, I've had the most experience with production customers deploying the code, and my company continues to invest lots of QA resources (racks, people and automation) to ensure the stability of target in stable kernels. Hence the consistent flow of bug-fixes to mainline, and to stable kernel releases. So once you stepped in over the holidays while I was out for a month after v4.9-rc and started sending driver maintainer patches and other minor changes to Linus, I was quite happy someone was helping out shepherding patches toward upstream. Since you've been doing a fine job pushing driver maintainer and other minor patches, I decided to let you run with it for a while. However, once you started proposing patches that are fatally flawed for basic operation in a complex area that I've repeatability objected to in the past, and also putting patches into linux-next that don't have any reviews and minimal testing, I start to get really concerned. So, I'll continue to focus on stability of the subsystem as a whole like I've always done, and use my production experience and company resources to ensure we don't take a step backwards stability wise in complex ares that have taken years to stabilize across the tree. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
