mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Richard Weinberger <richard@nod.at>,
	Markus Heiser <markus.heiser@darmarit.de>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 16/17] stable_kernel_rules.rst: Add cross-references to other ReST files
Date: Wed, 14 Sep 2016 20:06:01 -0300	[thread overview]
Message-ID: <9a819ea3d39cacdf6917de0b8570b59b66bb38d8.1473893776.git.mchehab@s-opensource.com> (raw)
In-Reply-To: <cover.1473893776.git.mchehab@s-opensource.com>
In-Reply-To: <cover.1473893776.git.mchehab@s-opensource.com>

Add two references for files that were already converted to ReST.

Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
---
 Documentation/development-process/stable_kernel_rules.rst | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/Documentation/development-process/stable_kernel_rules.rst b/Documentation/development-process/stable_kernel_rules.rst
index 533be00260e6..daa1073b65df 100644
--- a/Documentation/development-process/stable_kernel_rules.rst
+++ b/Documentation/development-process/stable_kernel_rules.rst
@@ -26,7 +26,9 @@ Rules on what kind of patches are accepted, and which ones are not, into the
    race can be exploited is also provided.
  - It cannot contain any "trivial" fixes in it (spelling changes,
    whitespace cleanups, etc).
- - It must follow the Documentation/development-process/SubmittingPatches.rst rules.
+ - It must follow the
+   :ref:`Documentation/development-process/SubmittingPatches.rst <submittingpatches>`
+   rules.
  - It or an equivalent fix must already exist in Linus' tree (upstream).
 
 
@@ -37,7 +39,8 @@ Procedure for submitting patches to the -stable tree
    submission guidelines as described in
    Documentation/networking/netdev-FAQ.txt
  - Security patches should not be handled (solely) by the -stable review
-   process but should follow the procedures in Documentation/development-process/SecurityBugs.rst.
+   process but should follow the procedures in
+   :ref:`Documentation/development-process/SecurityBugs.rst <securitybugs>`.
 
 For all other submissions, choose one of the following procedures
 -----------------------------------------------------------------
-- 
2.7.4

  parent reply	other threads:[~2016-09-14 23:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 23:05 [PATCH 00/17] Improve documentation for the development-process Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 01/17] HOWTO.rst: update information about generating documentation Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 02/17] HOWTO.rst: improve some markups to make it visually better Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 03/17] HOWTO.rst: adjust external link references Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 04/17] Changes.rst: add minimal requirements for documentation build Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 05/17] SubmitChecklist: update kernel-doc task Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 06/17] SubmitChecklist: convert it to ReST markup Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 07/17] SubmitChecklist: rename to RST and add to the development-proccess book Mauro Carvalho Chehab
2016-09-16  8:11   ` Jean Delvare
2016-09-14 23:05 ` [PATCH 08/17] doc-rst: add CSS styles for :kbd: and :menuselection: Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 09/17] email-clients.txt: convert it to ReST markup Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 10/17] email-clients.txt: add it to the development-process book Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 11/17] SubmittingPatches.rst: Add some cross-references Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 12/17] SubmittingPatches.rst: enrich the Sphinx output Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 13/17] SubmittingDrivers.rst: add a cross reference to CodingStyle Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 14/17] stable_api_nonsense.rst: fix emphasis on Sphinx Mauro Carvalho Chehab
2016-09-14 23:06 ` [PATCH 15/17] ManagementStyle.rst: avoid emphasis where not desired Mauro Carvalho Chehab
2016-09-14 23:06 ` Mauro Carvalho Chehab [this message]
2016-09-14 23:06 ` [PATCH 17/17] applying-patches.rst: Update the information there Mauro Carvalho Chehab

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=9a819ea3d39cacdf6917de0b8570b59b66bb38d8.1473893776.git.mchehab@s-opensource.com \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@infradead.org \
    --cc=mchehab@kernel.org \
    --cc=richard@nod.at \
    /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

all inboxes | Powered by JetHome®