The current wording on third option of stable kernel submission doesn't mention how to specify desired kernel version. Submitters reading the documentation could simply send multiple backported patches of the same upstream commit without any kernel version information, leaving stable maintainers and reviewers hard time to figure out the correct kernel version to be applied. Describe the subject prefix for specifying kernel version for the case above. Cc: stable@xxxxxxxxxxxxxxx Signed-off-by: Bagas Sanjaya <bagasdotme@xxxxxxxxx> --- This patch is sent as response to [1]. [1]: https://lore.kernel.org/stable/20221101074351.GA8310@amd/ Documentation/process/stable-kernel-rules.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst index 2fd8aa593a2851..409ae73c1ffcd1 100644 --- a/Documentation/process/stable-kernel-rules.rst +++ b/Documentation/process/stable-kernel-rules.rst @@ -77,7 +77,9 @@ Option 3 Send the patch, after verifying that it follows the above rules, to stable@xxxxxxxxxxxxxxx. You must note the upstream commit ID in the changelog of your submission, as well as the kernel version you wish -it to be applied to. +it to be applied to by adding desired kernel version number to the +patch subject prefix. For example, patches targeting 5.15 kernel should +have ``[PATCH 5.15]`` prefix. :ref:`option_1` is **strongly** preferred, is the easiest and most common. :ref:`option_2` and :ref:`option_3` are more useful if the patch isn't deemed base-commit: 30a0b95b1335e12efef89dd78518ed3e4a71a763 -- An old man doll... just what I always wanted! - Clara
