linux.git/Documentation/process/stable-kernel-rules.rst, branch v6.6.131

docs: stable-kernel-rules: mention that regressions must be prevented

2023-08-12T11:03:28+00:00

Document that changes intended for a specific stable series have to be
in all newer series still maintained, as otherwise users would run into
regressions.

CC: Greg KH 
CC: Sasha Levin 
CC: Jonathan Corbet 
Signed-off-by: Thorsten Leemhuis 
Link: https://lore.kernel.org/r/ddb5cb0d6b7aa4ef31642cd9657a0fb53d79cddb.1691219455.git.linux@leemhuis.info
Signed-off-by: Greg Kroah-Hartman

docs: stable-kernel-rules: fine-tune various details

2023-08-12T11:03:28+00:00

* various fine tuning to the text that cleans up rough edges the three
  previous preparatory patches left behind to keep the diffs simpler
* s/Linus' tree/mainline/g, as that's the term more commonly used and
  known
* create a short intro for the three submission options and streamline
  the explanation when to use which of them
* fix a >= vs <= thinko in an example to make it more straight forward
* there were two blank lines before some sub-headings and just one
  before others; use the former style everywhere

CC: Greg KH 
CC: Sasha Levin 
CC: Jonathan Corbet 
Signed-off-by: Thorsten Leemhuis 
Link: https://lore.kernel.org/r/e1960a70acae2c2f18b838aee9f8bf6055fae89b.1691219455.git.linux@leemhuis.info
Signed-off-by: Greg Kroah-Hartman

docs: stable-kernel-rules: make the examples for option 1 a proper list

2023-08-12T11:03:28+00:00

Separate the description for option 1 and the examples how to use it by
making the latter an indented unordered list.

No text changes.

CC: Greg KH 
CC: Sasha Levin 
CC: Jonathan Corbet 
Signed-off-by: Thorsten Leemhuis 
Link: https://lore.kernel.org/r/59deaabfabf0629d7cf2a52b196cec19d1f9ec47.1691219455.git.linux@leemhuis.info
Signed-off-by: Greg Kroah-Hartman

docs: stable-kernel-rules: move text around to improve flow

2023-08-12T11:03:28+00:00

Move the short description about when to use which of the submission
options to the top of the section, as it currently sits somewhat odd in
the middle between option 3 and examples of option 1.

Also move the examples of Option 1 into the section describing it (which
in the diff looks like option 2 and 3 are moving down).

No text changes, just moving it around.

CC: Greg KH 
CC: Sasha Levin 
CC: Jonathan Corbet 
Signed-off-by: Thorsten Leemhuis 
Link: https://lore.kernel.org/r/16f2377ee40dd7dfa146727fcbe7d1ebccf5b5be.1691219455.git.linux@leemhuis.info
Signed-off-by: Greg Kroah-Hartman

docs: stable-kernel-rules: improve structure by changing headlines

2023-08-12T11:03:28+00:00

* replace a needless sub-heading with a short intro sentence
* make "Following the submission" a proper sub-section with a headline
  without changing the text of the section

CC: Greg KH 
CC: Sasha Levin 
CC: Jonathan Corbet 
Signed-off-by: Thorsten Leemhuis 
Link: https://lore.kernel.org/r/0737676f951050b2ec39e1662ffea37d77ef0bec.1691219455.git.linux@leemhuis.info
Signed-off-by: Greg Kroah-Hartman

docs: stable-kernel-rules: make rule section more straight forward

2023-08-05T06:31:41+00:00

Tweak some of the rule text to make things more straight forward, with
the goal to stick closely to the intend of the old text:

* put the "it or equivalent fix must be upstream" rule at the top, as
  it's one of the most important ones that at the same time often seems
  to be missed by developers.
* "It must fix only one thing" was dropped, as that is almost always a
  thing that needs to be handled earlier when the change is mainlined.
  Furthermore, this is already indirectly covered by the "Separate your
  changes" section in Documentation/process/submitting-patches.rst which
  the rules already point to.
* six other rules are in the end one rule with clarifications; structure
  the text accordingly to make it a lot easier to follow and understand
  the intend.
* drop the 'In short, something critical' from one of those notes: it
  contradicts the "real bug that bothers people" aspect somewhat and does
  not really add anything

CC: Greg KH 
CC: Sasha Levin 
CC: Jonathan Corbet 
Signed-off-by: Thorsten Leemhuis 
Link: https://lore.kernel.org/r/f83e812879caa978a51a1a7cae7c359f29fc093c.1689056247.git.linux@leemhuis.info
Signed-off-by: Greg Kroah-Hartman

docs: stable-kernel-rules: mention other usages for stable tag comments

2023-08-05T06:31:41+00:00

Document how to delay backporting or send a note to the stable team
using shell-style inline comments attached to stable tags.

CC: Greg KH 
CC: Sasha Levin 
CC: Jonathan Corbet 
Signed-off-by: Thorsten Leemhuis 
Link: https://lore.kernel.org/r/bf1489b40ff358b7cb4f7d8cc73d5c7c3c143471.1689056247.git.linux@leemhuis.info
Signed-off-by: Greg Kroah-Hartman

Documentation/security-bugs: move from admin-guide/ to process/

2023-03-12T14:56:43+00:00

Jiri Kosina, Jonathan Corbet, and Willy Tarreau all expressed a desire
to move this document under process/.

Create a new section for security issues in the index and group it with
embargoed-hardware-issues.

I'm doing this at the start of the series to make all the subsequent
changes show up in 'git blame'.

Existing references were updated using:

  git grep -l security-bugs ':!Documentation/translations/' | xargs sed -i 's|admin-guide/security-bugs|process/security-bugs|g'
  git grep -l security-bugs Documentation/translations/ | xargs sed -i 's|Documentation/admin-guide/security-bugs|Documentation/process/security-bugs|g'
  git grep -l security-bugs Documentation/translations/ | xargs sed -i '/Original:/s|\.\./admin-guide/security-bugs|\.\./process/security-bugs|g'

Notably, the page is not moved in the translations (due to my lack of
knowledge of these languages), but the translations have been updated
to point to the new location of the original document where these
references exist.

Link: https://lore.kernel.org/all/nycvar.YFH.7.76.2206062326230.10851@cbobk.fhfr.pm/
Suggested-by: Jiri Kosina 
Cc: Alex Shi 
Cc: Yanteng Si 
Cc: Hu Haowen 
Cc: Federico Vaga 
Cc: Tsugikazu Shibata 
Cc: Minchan Kim 
Cc: Jeimi Lee 
Cc: Carlos Bilbao 
Cc: Akira Yokosawa 
Signed-off-by: Vegard Nossum 
Acked-by: Carlos Bilbao 
Reviewed-by: Yanteng Si 
Reviewed-by: Akira Yokosawa 
Acked-by: Federico Vaga 
Reviewed-by: Bagas Sanjaya 
Link: https://lore.kernel.org/r/20230305220010.20895-2-vegard.nossum@oracle.com
Signed-off-by: Greg Kroah-Hartman

Documentation: stable: Document alternative for referring upstream commit hash

2022-09-27T19:21:44+00:00

Additionally to the "commit  upstream." variant, "[ Upstream
commit  ]" is used as well as alternative to refer to the upstream
commit hash.

Signed-off-by: Salvatore Bonaccorso 
Link: https://lore.kernel.org/r/20220901184328.4075701-1-carnil@debian.org
Signed-off-by: Jonathan Corbet

Documentation: update stable review cycle documentation

2022-03-18T13:32:49+00:00

In recent times, the review cycle for stable releases have been changed.
In particular, there is release candidate phase between ACKing patches
and new stable release. Also, in case of failed submissions (fail to
apply to stable tree), manual backport (Option 3) have to be submitted
instead.

Update the release cycle documentation on stable-kernel-rules.rst to
reflect the above.

Cc: Sasha Levin 
Cc: Jonathan Corbet 
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Bagas Sanjaya 
Link: https://lore.kernel.org/r/20220314113329.485372-4-bagasdotme@gmail.com
Signed-off-by: Greg Kroah-Hartman