linux-kernel - [PATCH] Documentation: stable: clarify patch series prerequisites

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Wed,  9 Aug 2023 12:29:42 -0400
From:   Hugo Villeneuve <hugo@...ovil.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Sasha Levin <sashal@...nel.org>,
        Jonathan Corbet <corbet@....net>
Cc:     hugo@...ovil.com, andy.shevchenko@...il.com,
        Hugo Villeneuve <hvilleneuve@...onoff.com>,
        stable@...r.kernel.org, workflows@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH] Documentation: stable: clarify patch series prerequisites

From: Hugo Villeneuve <hvilleneuve@...onoff.com>

Add some clarifications for patches that have dependencies within the
patch series.

Signed-off-by: Hugo Villeneuve <hvilleneuve@...onoff.com>
---
This patch was made after some discussions I had with Greg and Andy when
submitting a series of patches for stable inclusion:

Link: https://lkml.org/lkml/2023/8/4/21

 Documentation/process/stable-kernel-rules.rst | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
index 51df1197d5ab..1c38ee009ed4 100644
--- a/Documentation/process/stable-kernel-rules.rst
+++ b/Documentation/process/stable-kernel-rules.rst
@@ -124,6 +124,18 @@ The tag sequence has the meaning of:
      git cherry-pick fd21073
      git cherry-pick <this commit>
 
+Note that for a patch series, you do not have to list as prerequisites the
+patches present in the series itself. For example, if you have the following
+patch series:
+
+.. code-block:: none
+
+     patch1
+     patch2
+
+where patch2 depends on patch1, you do not have to list patch1 as prerequisite
+of patch2 if you have already marked patch1 for stable inclusion.
+
 Also, some patches may have kernel version prerequisites.  This can be
 specified in the following format in the sign-off area:
 

base-commit: 13b9372068660fe4f7023f43081067376582ef3c
-- 
2.30.2