>> Anything that is an urgent and/or very small fix should just be against >> Linus' current tree and will go into the drivers branch for that tree. > >> Anything bigger and/or less urgent should be sent against the drivers >> branch for the next release.
> Linux 3.17 has been released. The current merge window is the one for > 3.18, expected to be closed in about a week. So urgent patches go into > that, maybe with a Cc to sta...@vger.kernel.org if they fix regressions. I may not have understood you correctly. My understanding is "Linus' current tree and will go into the drivers branch for that tree." would imply scsi-queue/drivers-for-3.17. "drivers branch for next release" would imply be scsi-queue/drivers-for-3.18 So all patches go into drivers-for-3.18, but the ones fixing regressions need a CC to sta...@vger.kernel.org ? Either way, drivers-for-3.18 is fine. Please apply there -Anish -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
