On Mon, Dec 26, 2016 at 11:48 AM, Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > Hi, > > On 26-12-16 00:25, Rafael J. Wysocki wrote: >> >> CC Mika and Andy. >> >> Plus I don't think -stable is going to take your patches directly. > > > Not sure what you mean with this remark? According to: > > Documentation/stable_kernel_rules.txt > > Option 1 > ******** > > To have the patch automatically included in the stable tree, add the tag > > .. code-block:: none > > Cc: stable@xxxxxxxxxxxxxxx > > in the sign-off area. Once the patch is merged it will be applied to > the stable tree without anything else needing to be done by the author > or subsystem maintainer. > > So yes, it won't get merged until it has been merged into Linus' > tree. But AFAICT adding Cc: stable@xxxxxxxxxxxxxxx is the right way > to indicate that a patch is a bug-fix which should be applied to > stable kernels once merged, which is my intention of adding the Cc. Yes, you can add a CC: <stable@...> tag to indicate that the patch is -stable material (in which case please also indicate which -stable series you want it to go to). No, you should not CC -stable on the patch submission. The CC: <stable@...> tag is for the maintainer you're sending the patch to rather than for -stable itself. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
