Skip to contentSkip to conversation

4.4 SCSI queue status

DISCUSSION Martin K. Petersen 2 participants 2 messages Nov 12, 2015 – Nov 13, 2015 SCSI

lore
Share & tools
lore
#0 lore raw

As some of you may have noticed, I have been volunteered to help with the SCSI tree going forward. Much like Christoph did for while. My current tree is here:

http://git.kernel.org/cgit/linux/kernel/git/mkp/linux.git/log/?h=4.4/scsi-queue

At this point I am done merging SCSI patches for 4.4. There was quite the backlog and I probably missed a bunch. Sorry!

However, save for a couple of patch series from Hannes my SCSI folder is now empty. Which means that for me to see something you will have to resend to linux-scsi.

Most of my merge cycles have been spent on driver updates. I prioritized those over core changes since we were essentially in the merge window when I got enlisted(*). Will tackle the trickier core stuff for 4.5.

There were a couple of driver series that just missed the cut: The HiSilicon SAS driver which required minor tweaks and two ufs patch series which required comment feedback and/or reviews.

The rules of engagement haven't changed. Here they are, slightly updated from the original version to reflect the omnipresent kbuild test robot and a few other things:

- A patch needs two positive reviews (non-author signoff, acked-by, reviewed-by or tested-by).

- The patch must have been posted to linux-scsi and nobody has expressed any concerns about it.

- The patch applies cleanly. Use checkpatch and git send-email.

- The patch compiles without warnings on all relevant architectures and does not incur any 0-day kbuild test robot complaints.

- Core changes survive a full xfstests run.

- The patch must have a commit message that comprehensively describes what the patch does. Do not link to vendor bugzilla entries that require special access credentials. If there is anything of importance in bugzilla, put it in the commit message.

- Resend the patches if you haven't received any feedback after a couple of weeks.

- When you resend a patch or series make sure to record all existing reviewed-by/acked-by/tested-by tags.

- Ping the list for additional reviewers.

(*) I will never merge during the merge window again!
I will never merge during the merge window again! I will never merge during the merge window again!

Signature · 1 line
Martin K. Petersen	Oracle Linux Engineering
#1 lore raw
Quoted 4 lines · Martin K. Petersen

As some of you may have noticed, I have been volunteered to help with the SCSI tree going forward. Much like Christoph did for while. My current tree is here:

It would be good to update MAINTAINERS with your address and a pointer to the git tree so that people are less confused.