linux-kernel - [PATCH] Documentation: process: Describe kernel version prefix for third option

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20221101131743.371340-1-bagasdotme@gmail.com>
Date:   Tue,  1 Nov 2022 20:17:43 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     stable@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Sasha Levin <sashal@...nel.org>,
        Jonathan Corbet <corbet@....net>, Pavel Machek <pavel@...x.de>,
        Biju Das <biju.das.jz@...renesas.com>,
        Bagas Sanjaya <bagasdotme@...il.com>
Subject: [PATCH] Documentation: process: Describe kernel version prefix for third option

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@...r.kernel.org
Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
---
 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@...r.kernel.org.  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