linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/4] Documentation: make option lists subsection of "Procedure for submitting patches to the -stable tree" in stable-kernel-rules.rst
Date: Sat, 12 Mar 2022 15:00:40 +0700	[thread overview]
Message-ID: <20220312080043.37581-2-bagasdotme@gmail.com> (raw)
In-Reply-To: <20220312080043.37581-1-bagasdotme@gmail.com>

The table of contents generated for stable-kernel-rules.rst contains
"For all other submissions..." section, that includes options
subsections. These options subsections should have been subsections of
"Procedure for submitting patches..." section. Remove the redundant
section.

Also, convert note about security patches to use `.. note::` block.

Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
 Documentation/process/stable-kernel-rules.rst | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
index 003c865e9c2..d8ce4c0c775 100644
--- a/Documentation/process/stable-kernel-rules.rst
+++ b/Documentation/process/stable-kernel-rules.rst
@@ -35,12 +35,13 @@ Rules on what kind of patches are accepted, and which ones are not, into the
 Procedure for submitting patches to the -stable tree
 ----------------------------------------------------
 
- - Security patches should not be handled (solely) by the -stable review
+.. note::
+
+   Security patches should not be handled (solely) by the -stable review
    process but should follow the procedures in
    :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>`.
 
-For all other submissions, choose one of the following procedures
------------------------------------------------------------------
+There are three options:
 
 .. _option_1:
 
-- 
An old man doll... just what I always wanted! - Clara


  reply	other threads:[~2022-03-12  8:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-12  8:00 [PATCH 0/4] Stable kernel release process update Bagas Sanjaya
2022-03-12  8:00 ` Bagas Sanjaya [this message]
2022-03-12  9:42   ` [PATCH 1/4] Documentation: make option lists subsection of "Procedure for submitting patches to the -stable tree" in stable-kernel-rules.rst Greg Kroah-Hartman
2022-03-14  6:39     ` Bagas Sanjaya
2022-03-12  8:00 ` [PATCH 2/4] Documentation: update stable review cycle documentation Bagas Sanjaya
2022-03-12  9:40   ` Greg Kroah-Hartman
2022-03-14  6:37     ` Bagas Sanjaya
2022-03-12  8:00 ` [PATCH 3/4] Documentation: add link to stable release candidate tree Bagas Sanjaya
2022-03-12  9:44   ` Greg Kroah-Hartman
2022-03-12  8:00 ` [PATCH 4/4] Documentation: update stable tree link Bagas Sanjaya
2022-03-12  9:41   ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220312080043.37581-2-bagasdotme@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).