[PATCH v2 19/20] doc: adjust references to development-process

From: Mauro Carvalho Chehab <hidden>
Date: 2016-09-13 02:18:10

Several files got moved into development-process, and had
a .rst appended. Fix references where it occurs.

Signed-off-by: Mauro Carvalho Chehab <redacted>
---
 Documentation/ABI/README                           |  2 +-
 Documentation/BUG-HUNTING                          |  2 +-
 Documentation/DocBook/kernel-hacking.tmpl          |  4 ++--
 Documentation/SubmitChecklist                      |  4 ++--
 Documentation/adding-syscalls.txt                  |  2 +-
 Documentation/development-process/4.Coding.rst     |  2 +-
 Documentation/development-process/5.Posting.rst    |  4 ++--
 Documentation/development-process/HOWTO.rst        | 22 ++++++++---------
 .../development-process/SubmittingDrivers.rst      |  4 ++--
 .../development-process/SubmittingPatches.rst      | 10 ++++----
 .../development-process/stable_kernel_rules.rst    |  4 ++--
 .../devicetree/bindings/submitting-patches.txt     |  2 +-
 Documentation/filesystems/locks.txt                |  2 +-
 Documentation/hwmon/submitting-patches             |  6 ++---
 Documentation/isdn/README                          |  2 +-
 Documentation/ja_JP/HOWTO                          | 28 +++++++++++-----------
 Documentation/ja_JP/SubmitChecklist                |  2 +-
 Documentation/ja_JP/SubmittingPatches              | 14 +++++------
 Documentation/ja_JP/stable_api_nonsense.txt        |  4 ++--
 Documentation/ja_JP/stable_kernel_rules.txt        |  6 ++---
 Documentation/ko_KR/HOWTO                          | 28 +++++++++++-----------
 Documentation/ko_KR/stable_api_nonsense.txt        |  4 ++--
 Documentation/networking/PLIP.txt                  |  2 +-
 Documentation/networking/netdev-FAQ.txt            |  8 +++----
 Documentation/scsi/scsi_mid_low_api.txt            |  2 +-
 Documentation/virtual/kvm/review-checklist.txt     |  4 ++--
 .../watchdog/convert_drivers_to_kernel_api.txt     |  2 +-
 Documentation/zh_CN/CodingStyle                    |  4 ++--
 Documentation/zh_CN/HOWTO                          | 28 +++++++++++-----------
 Documentation/zh_CN/SecurityBugs                   |  4 ++--
 Documentation/zh_CN/SubmittingDrivers              |  8 +++----
 Documentation/zh_CN/SubmittingPatches              | 10 ++++----
 Documentation/zh_CN/stable_api_nonsense.txt        |  4 ++--
 Documentation/zh_CN/stable_kernel_rules.txt        |  6 ++---
 MAINTAINERS                                        |  2 +-
 README                                             |  4 ++--
 REPORTING-BUGS                                     |  2 +-
 drivers/net/ppp/Kconfig                            |  2 +-
 drivers/pcmcia/Kconfig                             |  2 +-
 fs/Kconfig.binfmt                                  |  2 +-
 fs/fuse/Kconfig                                    |  2 +-
 net/Kconfig                                        |  4 ++--
 scripts/ver_linux                                  |  2 +-
 tools/testing/selftests/futex/README               |  2 +-
 44 files changed, 132 insertions(+), 132 deletions(-)

diff --git a/Documentation/ABI/README b/Documentation/ABI/README
index 1fafc4b0753b..232cade3a59c 100644
--- a/Documentation/ABI/README
+++ b/Documentation/ABI/README

@@ -84,4 +84,4 @@ stable:
 
 - Kernel-internal symbols.  Do not rely on the presence, absence, location, or
   type of any kernel symbol, either in System.map files or the kernel binary
-  itself.  See Documentation/stable_api_nonsense.txt.
+  itself.  See Documentation/development-process/stable_api_nonsense.rst.

diff --git a/Documentation/BUG-HUNTING b/Documentation/BUG-HUNTING
index 65022a87bf17..e0e4637fb30a 100644
--- a/Documentation/BUG-HUNTING
+++ b/Documentation/BUG-HUNTING

@@ -242,5 +242,5 @@ Once you have worked out a fix please submit it upstream. After all open
 source is about sharing what you do and don't you want to be recognised for
 your genius?
 
-Please do read Documentation/SubmittingPatches though to help your code get
+Please do read Documentation/development-process/SubmittingPatches.rst though to help your code get
 accepted.

diff --git a/Documentation/DocBook/kernel-hacking.tmpl b/Documentation/DocBook/kernel-hacking.tmpl
index 589b40cc5eb5..562c0648738e 100644
--- a/Documentation/DocBook/kernel-hacking.tmpl
+++ b/Documentation/DocBook/kernel-hacking.tmpl

@@ -1208,8 +1208,8 @@ static struct block_device_operations opt_fops = {
    
    <listitem>
     <para>
-     Finally, don't forget to read <filename>Documentation/SubmittingPatches</filename>
-     and possibly <filename>Documentation/SubmittingDrivers</filename>.
+     Finally, don't forget to read <filename>Documentation/development-process/SubmittingPatches.rst</filename>
+     and possibly <filename>Documentation/development-process/SubmittingDrivers.rst</filename>.
     </para>
    </listitem>
   </itemizedlist>

diff --git a/Documentation/SubmitChecklist b/Documentation/SubmitChecklist
index 2b7e32dfe00d..d646b1d47db1 100644
--- a/Documentation/SubmitChecklist
+++ b/Documentation/SubmitChecklist

@@ -5,7 +5,7 @@ Here are some basic things that developers should do if they want to see their
 kernel patch submissions accepted more quickly.
 
 These are all above and beyond the documentation that is provided in
-Documentation/SubmittingPatches and elsewhere regarding submitting Linux
+Documentation/development-process/SubmittingPatches.rst and elsewhere regarding submitting Linux
 kernel patches.

@@ -27,7 +27,7 @@ kernel patches.
    tends to use `unsigned long' for 64-bit quantities.
 
 5: Check your patch for general style as detailed in
-   Documentation/CodingStyle.  Check for trivial violations with the
+   Documentation/development-process/CodingStyle.rst.  Check for trivial violations with the
    patch style checker prior to submission (scripts/checkpatch.pl).
    You should be able to justify all violations that remain in
    your patch.

diff --git a/Documentation/adding-syscalls.txt b/Documentation/adding-syscalls.txt
index bbb31e091b28..7dd00b344844 100644
--- a/Documentation/adding-syscalls.txt
+++ b/Documentation/adding-syscalls.txt

@@ -3,7 +3,7 @@ Adding a New System Call
 
 This document describes what's involved in adding a new system call to the
 Linux kernel, over and above the normal submission advice in
-Documentation/SubmittingPatches.
+Documentation/development-process/SubmittingPatches.rst.
 
 
 System Call Alternatives

diff --git a/Documentation/development-process/4.Coding.rst b/Documentation/development-process/4.Coding.rst
index 9d5cef996f7f..a52465835c7b 100644
--- a/Documentation/development-process/4.Coding.rst
+++ b/Documentation/development-process/4.Coding.rst

@@ -22,7 +22,7 @@ Coding style
 ************
 
 The kernel has long had a standard coding style, described in
-Documentation/CodingStyle.  For much of that time, the policies described
+Documentation/development-process/CodingStyle.rst.  For much of that time, the policies described
 in that file were taken as being, at most, advisory.  As a result, there is
 a substantial amount of code in the kernel which does not meet the coding
 style guidelines.  The presence of that code leads to two independent

diff --git a/Documentation/development-process/5.Posting.rst b/Documentation/development-process/5.Posting.rst
index b511ddf7e82a..d75260f4fc1d 100644
--- a/Documentation/development-process/5.Posting.rst
+++ b/Documentation/development-process/5.Posting.rst

@@ -210,7 +210,7 @@ The tags in common use are:
  - Signed-off-by: this is a developer's certification that he or she has
    the right to submit the patch for inclusion into the kernel.  It is an
    agreement to the Developer's Certificate of Origin, the full text of
-   which can be found in Documentation/SubmittingPatches.  Code without a
+   which can be found in Documentation/development-process/SubmittingPatches.rst.  Code without a
    proper signoff cannot be merged into the mainline.
 
  - Acked-by: indicates an agreement by another developer (often a

@@ -221,7 +221,7 @@ The tags in common use are:
    it to work.
 
  - Reviewed-by: the named developer has reviewed the patch for correctness;
-   see the reviewer's statement in Documentation/SubmittingPatches for more
+   see the reviewer's statement in Documentation/development-process/SubmittingPatches.rst for more
    detail.
 
  - Reported-by: names a user who reported a problem which is fixed by this

diff --git a/Documentation/development-process/HOWTO.rst b/Documentation/development-process/HOWTO.rst
index 31c8df5d20c7..9a06de24b755 100644
--- a/Documentation/development-process/HOWTO.rst
+++ b/Documentation/development-process/HOWTO.rst

@@ -90,19 +90,19 @@ required reading:
     what is necessary to do to configure and build the kernel.  People
     who are new to the kernel should start here.
 
-  :ref:`Documentation/Changes <changes>`
+  :ref:`Documentation/development-process/Changes.rst <changes>`
     This file gives a list of the minimum levels of various software
     packages that are necessary to build and run the kernel
     successfully.
 
-  :ref:`Documentation/CodingStyle <codingstyle>`
+  :ref:`Documentation/development-process/CodingStyle.rst <codingstyle>`
     This describes the Linux kernel coding style, and some of the
     rationale behind it. All new code is expected to follow the
     guidelines in this document. Most maintainers will only accept
     patches if these rules are followed, and many people will only
     review code if it is in the proper style.
 
-  :ref:`Documentation/SubmittingPatches <submittingpatches>` and :ref:`Documentation/SubmittingDrivers <submittingdrivers>`
+  :ref:`Documentation/development-process/SubmittingPatches.rst <submittingpatches>` and :ref:`Documentation/development-process/SubmittingDrivers.rst <submittingdrivers>`
     These files describe in explicit detail how to successfully create
     and send a patch, including (but not limited to):

@@ -124,7 +124,7 @@ required reading:
 
 		http://linux.yyz.us/patch-format.html
 
-  :ref:`Documentation/stable_api_nonsense.txt <stable_api_nonsense>`
+  :ref:`Documentation/development-process/stable_api_nonsense.rst <stable_api_nonsense>`
     This file describes the rationale behind the conscious decision to
     not have a stable API within the kernel, including things like:

@@ -137,29 +137,29 @@ required reading:
     philosophy and is very important for people moving to Linux from
     development on other Operating Systems.
 
-  :ref:`Documentation/SecurityBugs <securitybugs>`
+  :ref:`Documentation/development-process/SecurityBugs.rst <securitybugs>`
     If you feel you have found a security problem in the Linux kernel,
     please follow the steps in this document to help notify the kernel
     developers, and help solve the issue.
 
-  :ref:`Documentation/ManagementStyle <managementstyle>`
+  :ref:`Documentation/development-process/ManagementStyle.rst <managementstyle>`
     This document describes how Linux kernel maintainers operate and the
     shared ethos behind their methodologies.  This is important reading
     for anyone new to kernel development (or anyone simply curious about
     it), as it resolves a lot of common misconceptions and confusion
     about the unique behavior of kernel maintainers.
 
-  :ref:`Documentation/stable_kernel_rules.txt <stable_kernel_rules>`
+  :ref:`Documentation/development-process/stable_kernel_rules.rst <stable_kernel_rules>`
     This file describes the rules on how the stable kernel releases
     happen, and what to do if you want to get a change into one of these
     releases.
 
-  :ref:`Documentation/kernel-docs.txt <kernel_docs>`
+  :ref:`Documentation/development-process/kernel-docs.rst <kernel_docs>`
     A list of external documentation that pertains to kernel
     development.  Please consult this list if you do not find what you
     are looking for within the in-kernel documentation.
 
-  :ref:`Documentation/applying-patches.txt <applying_patches>`
+  :ref:`Documentation/development-process/applying-patches.rst <applying_patches>`
     A good introduction describing exactly what a patch is and how to
     apply it to the different development branches of the kernel.

@@ -301,7 +301,7 @@ two weeks, but it can be longer if there are no pressing problems.  A
 security-related problem, instead, can cause a release to happen almost
 instantly.
 
-The file Documentation/stable_kernel_rules.txt in the kernel tree
+The file Documentation/development-process/stable_kernel_rules.rst in the kernel tree
 documents what kinds of changes are acceptable for the -stable tree, and
 how the release process works.

@@ -433,7 +433,7 @@ add your statements between the individual quoted sections instead of
 writing at the top of the mail.
 
 If you add patches to your mail, make sure they are plain readable text
-as stated in Documentation/SubmittingPatches. Kernel developers don't
+as stated in Documentation/development-process/SubmittingPatches.rst. Kernel developers don't
 want to deal with attachments or compressed patches; they may want
 to comment on individual lines of your patch, which works only that way.
 Make sure you use a mail program that does not mangle spaces and tab

diff --git a/Documentation/development-process/SubmittingDrivers.rst b/Documentation/development-process/SubmittingDrivers.rst
index 2ac931645e53..621d17af20fd 100644
--- a/Documentation/development-process/SubmittingDrivers.rst
+++ b/Documentation/development-process/SubmittingDrivers.rst

@@ -8,7 +8,7 @@ various kernel trees. Note that if you are interested in video card drivers
 you should probably talk to XFree86 (http://www.xfree86.org/) and/or X.Org
 (http://x.org/) instead.
 
-Also read the Documentation/SubmittingPatches document.
+Also read the Documentation/development-process/SubmittingPatches.rst document.
 
 
 Allocating Device Numbers

@@ -73,7 +73,7 @@ Interfaces:
 
 Code:
 		Please use the Linux style of code formatting as documented
-		in Documentation/CodingStyle. If you have sections of code
+		in Documentation/development-process/CodingStyle.rst. If you have sections of code
 		that need to be in other formats, for example because they
 		are shared with a windows driver kit and you want to
 		maintain them just once separate them out nicely and note

diff --git a/Documentation/development-process/SubmittingPatches.rst b/Documentation/development-process/SubmittingPatches.rst
index d856af3de9f5..b0bf22510c3d 100644
--- a/Documentation/development-process/SubmittingPatches.rst
+++ b/Documentation/development-process/SubmittingPatches.rst

@@ -13,7 +13,7 @@ format.  For detailed information on how the kernel development process
 works, see Documentation/development-process.  Also, read
 Documentation/SubmitChecklist for a list of items to check before
 submitting code.  If you are submitting a driver, also read
-Documentation/SubmittingDrivers; for device tree binding patches, read
+Documentation/development-process/SubmittingDrivers.rst; for device tree binding patches, read
 Documentation/devicetree/bindings/submitting-patches.txt.
 
 Many of these steps describe the default behavior of the git version

@@ -246,7 +246,7 @@ Style-check your changes
 ------------------------
 
 Check your patch for basic style violations, details of which can be
-found in Documentation/CodingStyle.  Failure to do so simply wastes
+found in Documentation/development-process/CodingStyle.rst.  Failure to do so simply wastes
 the reviewers time and will get your patch rejected, probably
 without even being read.

@@ -313,7 +313,7 @@ toward the stable maintainers by putting a line like this:
   Cc: stable@vger.kernel.org
 
 into the sign-off area of your patch (note, NOT an email recipient).  You
-should also read Documentation/stable_kernel_rules.txt in addition to this
+should also read Documentation/development-process/stable_kernel_rules.rst in addition to this
 file.
 
 Note, however, that some subsystem maintainers want to come to their own

@@ -843,8 +843,8 @@ Greg Kroah-Hartman, "How to piss off a kernel subsystem maintainer".
 NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!
   <https://lkml.org/lkml/2005/7/11/336>
 
-Kernel Documentation/CodingStyle:
-  <Documentation/CodingStyle>
+Kernel Documentation/development-process/CodingStyle.rst:
+  <Documentation/development-process/CodingStyle.rst>
 
 Linus Torvalds's mail on the canonical patch format:
   <http://lkml.org/lkml/2005/4/7/183>

diff --git a/Documentation/development-process/stable_kernel_rules.rst b/Documentation/development-process/stable_kernel_rules.rst
index 1eba72708c7f..533be00260e6 100644
--- a/Documentation/development-process/stable_kernel_rules.rst
+++ b/Documentation/development-process/stable_kernel_rules.rst

@@ -26,7 +26,7 @@ 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/SubmittingPatches rules.
+ - It must follow the Documentation/development-process/SubmittingPatches.rst rules.
  - It or an equivalent fix must already exist in Linus' tree (upstream).

@@ -37,7 +37,7 @@ 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/SecurityBugs.
+   process but should follow the procedures in Documentation/development-process/SecurityBugs.rst.
 
 For all other submissions, choose one of the following procedures
 -----------------------------------------------------------------

diff --git a/Documentation/devicetree/bindings/submitting-patches.txt b/Documentation/devicetree/bindings/submitting-patches.txt
index 7d44eae7ab0b..5fa11b9b8410 100644
--- a/Documentation/devicetree/bindings/submitting-patches.txt
+++ b/Documentation/devicetree/bindings/submitting-patches.txt

@@ -3,7 +3,7 @@
 
 I. For patch submitters
 
-  0) Normal patch submission rules from Documentation/SubmittingPatches
+  0) Normal patch submission rules from Documentation/development-process/SubmittingPatches.rst
      applies.
 
   1) The Documentation/ portion of the patch should be a separate patch.

diff --git a/Documentation/filesystems/locks.txt b/Documentation/filesystems/locks.txt
index 2cf81082581d..8af1ee4a6399 100644
--- a/Documentation/filesystems/locks.txt
+++ b/Documentation/filesystems/locks.txt

@@ -19,7 +19,7 @@ forever.
 
 This should not cause problems for anybody, since everybody using a
 2.1.x kernel should have updated their C library to a suitable version
-anyway (see the file "Documentation/Changes".)
+anyway (see the file "Documentation/development-process/Changes.rst".)
 
 1.2 Allow Mixed Locks Again
 ---------------------------

diff --git a/Documentation/hwmon/submitting-patches b/Documentation/hwmon/submitting-patches
index 57f60307accc..371baf7a43e2 100644
--- a/Documentation/hwmon/submitting-patches
+++ b/Documentation/hwmon/submitting-patches

@@ -11,9 +11,9 @@ increase the chances of your change being accepted.
 
 * It should be unnecessary to mention, but please read and follow
     Documentation/SubmitChecklist
-    Documentation/SubmittingDrivers
-    Documentation/SubmittingPatches
-    Documentation/CodingStyle
+    Documentation/development-process/SubmittingDrivers.rst
+    Documentation/development-process/SubmittingPatches.rst
+    Documentation/development-process/CodingStyle.rst
 
 * Please run your patch through 'checkpatch --strict'. There should be no
   errors, no warnings, and few if any check messages. If there are any

diff --git a/Documentation/isdn/README b/Documentation/isdn/README
index cfb1884342ee..508817c06a53 100644
--- a/Documentation/isdn/README
+++ b/Documentation/isdn/README

@@ -321,7 +321,7 @@ README for the ISDN-subsystem
   ATTENTION!
 
   Always use the latest module utilities. The current version is
-  named in Documentation/Changes. Some old versions of insmod
+  named in Documentation/development-process/Changes.rst. Some old versions of insmod
   are not capable of setting the driver-Ids correctly.
 
 3. Lowlevel-driver configuration.

diff --git a/Documentation/ja_JP/HOWTO b/Documentation/ja_JP/HOWTO
index 581c14bdd7be..465b238e7d1d 100644
--- a/Documentation/ja_JP/HOWTO
+++ b/Documentation/ja_JP/HOWTO

@@ -1,5 +1,5 @@
 NOTE:
-This is a version of Documentation/HOWTO translated into Japanese.
+This is a version of Documentation/development-process/HOWTO.rst translated into Japanese.
 This document is maintained by Tsugikazu Shibata <tshibata@ab.jp.nec.com>
 and the JF Project team <www.linux.or.jp/JF>.
 If you find any difference between this document and the original file

@@ -14,7 +14,7 @@ to update the original English file first.
 Last Updated: 2013/07/19
 ==================================
 ããã¯ã
-linux-3.10/Documentation/HOWTO
+linux-3.10/Documentation/development-process/HOWTO.rst
 ã®åè¨³ã§ãã
 
 ç¿»è¨³å£ä½ï¼ JF ããã¸ã§ã¯ã < http://linuxjf.sourceforge.jp/ >

@@ -122,20 +122,20 @@ linux-api@ver.kernel.org ã«éããã¨ãå§ãã¾ãã
     ã¦ãã¾ããã«ã¼ãã«ã«é¢ãã¦åãã¦ã®äººã¯ããããã¹ã¿ã¼ãããã¨è¯ãã§
     ãããã
 
-  Documentation/Changes
+  Documentation/development-process/Changes.rst
      ãã®ãã¡ã¤ã«ã¯ã«ã¼ãã«ããã¾ãçæ(è¨³æ³¨ build )ããèµ°ãããã®ã«æ
      å°éã®ã¬ãã«ã§å¿

è¦ãªæ°ã
ã®ã½ããã¦ã§ã¢ããã±ã¼ã¸ã®ä¸è¦§ãç¤ºãã¦ã
      ã¾ãã
 
-  Documentation/CodingStyle
+  Documentation/development-process/CodingStyle.rst
     ããã¯ Linux ã«ã¼ãã«ã®ã³ã¼ãã£ã³ã°ã¹ã¿ã¤ã«ã¨èæ¯ã«ããçç±ãè¨è¿°
     ãã¦ãã¾ããå
¨ã¦ã®æ°ããã³ã¼ãã¯ãã®ããã¥ã¡ã³ãã«ããã¬ã¤ãã©ã¤ã³
     ã«å¾ã£ã¦ãããã¨ãæå¾
ããã¦ãã¾ããå¤§é¨åã®ã¡ã³ããã¯ãããã®ã«ã¼
     ã«ã«å¾ã£ã¦ãããã®ã ããåãä»ããå¤ãã®äººã¯æ£ããã¹ã¿ã¤ã«ã®ã³ã¼ã
     ã ããã¬ãã¥ã¼ãã¾ãã
 
-  Documentation/SubmittingPatches
-  Documentation/SubmittingDrivers
+  Documentation/development-process/SubmittingPatches.rst
+  Documentation/development-process/SubmittingDrivers.rst
      ãããã®ãã¡ã¤ã«ã«ã¯ãã©ããã£ã¦ãã¾ãããããä½ã£ã¦æç¨¿ãããã«
      ã¤ãã¦éå¸¸ã«è©³ããæ¸ããã¦ãããä»¥ä¸ãå«ã¿ã¾ã(ããã ãã«éããªã
      ããã©ã)

@@ -153,7 +153,7 @@ linux-api@ver.kernel.org ã«éããã¨ãå§ãã¾ãã
 	"Linux kernel patch submission format"
 		http://linux.yyz.us/patch-format.html
 
-  Documentation/stable_api_nonsense.txt
+  Documentation/development-process/stable_api_nonsense.rst
      ãã®ãã¡ã¤ã«ã¯ã«ã¼ãã«ã®ä¸­ã«ä¸å¤ã®APIãæããªããã¨ã«ããæè­çãª
      æ±ºæ­ã®èæ¯ã«ããçç±ã«ã¤ãã¦æ¸ããã¦ãã¾ããä»¥ä¸ã®ãããªãã¨ãå«
      ãã§ãã¾ã-
@@ -164,29 +164,29 @@ linux-api@ver.kernel.org ã«éããã¨ãå§ãã¾ãã
      ãã®ãã­ã¥ã¡ã³ãã¯ Linux éçºã®ææ³ãçè§£ããã®ã«éå¸¸ã«éè¦ã§ãã
      ããã¦ãä»ã®OSã§ã®éçºè

ã Linux ã«ç§»ãæã«ã¨ã¦ãéè¦ã§ãã
 
-  Documentation/SecurityBugs
+  Documentation/development-process/SecurityBugs.rst
     ãã Linux ã«ã¼ãã«ã§ã»ãã¥ãªãã£åé¡ãçºè¦ããããã«æã£ãããã
     ã®ããã¥ã¡ã³ãã®ã¹ãããã«å¾ã£ã¦ã«ã¼ãã«éçºè
ã«é£çµ¡ããåé¡è§£æ±ºã
     æ¯æ´ãã¦ãã ããã
 
-  Documentation/ManagementStyle
+  Documentation/development-process/ManagementStyle.rst
     ãã®ããã¥ã¡ã³ãã¯ Linux ã«ã¼ãã«ã®ã¡ã³ããéãã©ãè¡åãããã
     å½¼ãã®ææ³ã®èæ¯ã«ããå
±æããã¦ããç²¾ç¥ã«ã¤ãã¦è¨è¿°ãã¦ãã¾ããã
     ãã¯ã«ã¼ãã«éçºã®åå¿è
ãªãï¼ãããã¯ãåã«èå³ãããã ãã®äººã§ãï¼
     éè¦ã§ãããªããªããã®ããã¥ã¡ã³ãã¯ãã«ã¼ãã«ã¡ã³ããéã®ç¬ç¹ãª
     è¡åã«ã¤ãã¦ã®å¤ãã®èª¤è§£ãæ··ä¹±ãè§£æ¶ããããã§ãã
 
-  Documentation/stable_kernel_rules.txt
+  Documentation/development-process/stable_kernel_rules.rst
     ãã®ãã¡ã¤ã«ã¯ã©ã®ããã« stable ã«ã¼ãã«ã®ãªãªã¼ã¹ãè¡ããããã®ã«ã¼
     ã«ãè¨è¿°ããã¦ãã¾ããããã¦ãããã®ãªãªã¼ã¹ã®ä¸ã®ã©ããã§å¤æ´ãå
     ãå
¥ãã¦ãããããå ´åã«ä½ãããã°è¯ãããç¤ºããã¦ãã¾ãã
 
-  Documentation/kernel-docs.txt
+  Documentation/development-process/kernel-docs.rst
 ããã«ã¼ãã«éçºã«ä»éããå¤é¨ããã¥ã¡ã³ãã®ãªã¹ãã§ããããããªãã
     æ¢ãã¦ãããã®ãã«ã¼ãã«å
ã®ããã¥ã¡ã³ãã§ã¿ã¤ãããªãã£ãå ´åã
     ãã®ãªã¹ããããã£ã¦ã¿ã¦ãã ããã
 
-  Documentation/applying-patches.txt
+  Documentation/development-process/applying-patches.rst
     ãããã¨ã¯ãªã«ããããããã©ããã£ã¦æ§ã
ãªã«ã¼ãã«ã®éçºãã©ã³ãã«
     é©ç¨ããã®ãã«ã¤ãã¦æ£ç¢ºã«è¨è¿°ããè¯ãå
¥éæ¸ã§ãã

@@ -314,7 +314,7 @@ Andrew Morton ã Linux-kernel ã¡ã¼ãªã³ã°ãªã¹ãã«ã«ã¼ãã«ãªãªã¼
 ãåé¡ããªããã°ããå°ãé·ããªããã¨ãããã¾ããã»ã­ã¥ãªãã£é¢é£ã®åé¡
 ã®å ´åã¯ããã«å¯¾ãã¦ã ãããã®å ´åãããã«ãªãªã¼ã¹ãããã¾ãã
 
-ã«ã¼ãã«ããªã¼ã«å

¥ã£ã¦ãããDocumentation/stable_kernel_rules.txt ãã¡
+ã«ã¼ãã«ããªã¼ã«å
¥ã£ã¦ãããDocumentation/development-process/stable_kernel_rules.rst ãã¡
 ã¤ã«ã«ã¯ã©ã®ãããªç¨®é¡ã®å¤æ´ã -stable ããªã¼ã«åãå
¥ãå¯è½ããã¾ããª
 ãªã¼ã¹ããã»ã¹ãã©ãåãããè¨è¿°ããã¦ãã¾ãã

@@ -438,7 +438,7 @@ MAINTAINERS ãã¡ã¤ã«ã«ãªã¹ããããã¾ãã®ã§åç

§ãã¦ãã ã
 ã¡ã¼ã«ã®å
é ã§ãªããåå¼ç¨è¡ã®éã«ããªãã®è¨ããããã¨ãè¿½å ããã¹ãã§
 ãã
 
-ããããããã¡ã¼ã«ã«ä»ããå ´åã¯ãDocumentation/SubmittingPatches ã«æ
+ããããããã¡ã¼ã«ã«ä»ããå ´åã¯ãDocumentation/development-process/SubmittingPatches.rst ã«æ
 ç¤ºããã¦ããããã«ãããã¯ ãã¬ã¼ã³ãªå¯èªããã¹ãã«ãããã¨ãå¿ããªã
 ããã«ãã¾ããããã«ã¼ãã«éçºè
ã¯ æ·»ä»ãå§ç¸®ããããããæ±ããããã¾
 ãã-

diff --git a/Documentation/ja_JP/SubmitChecklist b/Documentation/ja_JP/SubmitChecklist
index cb5507b1ac81..c0020797d6b9 100644
--- a/Documentation/ja_JP/SubmitChecklist
+++ b/Documentation/ja_JP/SubmitChecklist

@@ -27,7 +27,7 @@ Linux ã«ã¼ãã«ãããæç¨¿è

åããã§ãã¯ãªã¹ã
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 æ¬æ¸ã§ã¯ãããããããç´ æ©ãåãè¾¼ãã§ãããããéçºè
ãå®è·µãã¹ãåºæ¬çãªäºæ
-ãããã¤ãç´¹ä»ãã¾ããããã«ããå
¨ã¦ã®äºæã¯ãDocumentation/SubmittingPatches
+ãããã¤ãç´¹ä»ãã¾ããããã«ããå
¨ã¦ã®äºæã¯ãDocumentation/development-process/SubmittingPatches.rst
 ãªã©ã®Linuxã«ã¼ãã«ãããæç¨¿ã«éãã¦ã®å¿å¾ãè£è¶³ãããã®ã§ãã
 
  1: å¦¥å½ãªCONFIGãªãã·ã§ã³ãå¤æ´ãããCONFIGãªãã·ã§ã³ãã¤ã¾ã =y, =m, =n

diff --git a/Documentation/ja_JP/SubmittingPatches b/Documentation/ja_JP/SubmittingPatches
index 5d6ae639bfa0..aed86762a6d3 100644
--- a/Documentation/ja_JP/SubmittingPatches
+++ b/Documentation/ja_JP/SubmittingPatches

@@ -1,5 +1,5 @@
 NOTE:
-This is a version of Documentation/SubmittingPatches into Japanese.
+This is a version of Documentation/development-process/SubmittingPatches.rst into Japanese.
 This document is maintained by Keiichi KII <k-keiichi@bx.jp.nec.com>
 and the JF Project team <http://www.linux.or.jp/JF/>.
 If you find any difference between this document and the original file

@@ -15,7 +15,7 @@ Last Updated: 2011/06/09
 
 ==================================
 ããã¯ã
-linux-2.6.39/Documentation/SubmittingPatches ã®åè¨³
+linux-2.6.39/Documentation/development-process/SubmittingPatches.rst ã®åè¨³
 ã§ãã
 ç¿»è¨³å£ä½ï¼ JF ããã¸ã§ã¯ã < http://www.linux.or.jp/JF/ >
 ç¿»è¨³æ¥ï¼ 2011/06/09

@@ -36,7 +36,7 @@ Linux ã«ã¼ãã«ã«å¤æ´ãå ãããã¨æã£ã¦ããåäººåã¯ä¼ç¤¾
 
 ã³ã¼ããæç¨¿ããåã«ãDocumentation/SubmitChecklist ã®é

ç®ãªã¹ãã«ç®
 ãéãã¦ãã§ãã¯ãã¦ãã ãããããããªãããã©ã¤ãã¼ãæç¨¿ãããã¨ã
-ã¦ãããªããDocumentation/SubmittingDrivers ã«ãç®ãéãã¦ãã ããã
+ã¦ãããªããDocumentation/development-process/SubmittingDrivers.rst ã«ãç®ãéãã¦ãã ããã
 
 --------------------------------------------
 ã»ã¯ã·ã§ã³1 ãããã®ä½ãæ¹ã¨éãæ¹

@@ -148,7 +148,7 @@ http://savannah.nongnu.org/projects/quilt
 4) ãããã®ã¹ã¿ã¤ã«ãã§ãã¯
 
 ããªãã®ããããåºæ¬çãª( Linux ã«ã¼ãã«ã®)ã³ã¼ãã£ã³ã°ã¹ã¿ã¤ã«ã«éåã
-ã¦ããªããããã§ãã¯ãã¦ä¸ããããã®è©³ç´°ã Documentation/CodingStyle ã§
+ã¦ããªããããã§ãã¯ãã¦ä¸ããããã®è©³ç´°ã Documentation/development-process/CodingStyle.rst ã§
 è¦ã¤ãããã¨ãã§ãã¾ããã³ã¼ãã£ã³ã°ã¹ã¿ã¤ã«ã®éåã¯ã¬ãã¥ã¼ããäººã®
 æéãç¡é§ã«ããã ããªã®ã§ãæããããªãã®ãããã¯èª­ã¾ãããã¨ãããªã
 æå¦ãããã§ãããã
@@ -609,7 +609,7 @@ diffstat ã®çµæãçæããããã«ã git diff -M --stat --summary ã
 ãä¾å¤ãé©ç¨ããã«ã¯ãæ¬å½ã«å¦¥å½ãªçç±ãä¸å¯æ¬ ã§ããããªãã¯æãããã®
 ã»ã¯ã·ã§ã³ã Linus ã®ã³ã³ãã¥ã¼ã¿ã»ãµã¤ã¨ã³ã¹101ã¨å¼ã¶ã§ãããã
 
-1) Documentation/CodingStyleãåç

§
+1) Documentation/development-process/CodingStyle.rstãåç
§
 
 è¨ãã¾ã§ããªããããªãã®ã³ã¼ãããã®ã³ã¼ãã£ã³ã°ã¹ã¿ã¤ã«ãããã¾ãã«
 ãé¸è±ãã¦ããã¨ãã¬ãã¥ã¼ãã³ã¡ã³ããªãã«åãåã£ã¦ããããªãããã

@@ -704,8 +704,8 @@ Greg Kroah-Hartman, "How to piss off a kernel subsystem maintainer".
 NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!
   <https://lkml.org/lkml/2005/7/11/336>
 
-Kernel Documentation/CodingStyle:
-  <http://users.sosdg.org/~qiyong/lxr/source/Documentation/CodingStyle>
+Kernel Documentation/development-process/CodingStyle.rst:
+  <http://users.sosdg.org/~qiyong/lxr/source/Documentation/development-process/CodingStyle.rst>
 
 Linus Torvalds's mail on the canonical patch format:
   <http://lkml.org/lkml/2005/4/7/183>

diff --git a/Documentation/ja_JP/stable_api_nonsense.txt b/Documentation/ja_JP/stable_api_nonsense.txt
index 7653b5cbfed2..fa54dc9ee9f0 100644
--- a/Documentation/ja_JP/stable_api_nonsense.txt
+++ b/Documentation/ja_JP/stable_api_nonsense.txt

@@ -1,5 +1,5 @@
 NOTE:
-This is a version of Documentation/stable_api_nonsense.txt into Japanese.
+This is a version of Documentation/development-process/stable_api_nonsense.rst into Japanese.
 This document is maintained by IKEDA, Munehiro <m-ikeda@ds.jp.nec.com>
 and the JF Project team <http://www.linux.or.jp/JF/>.
 If you find any difference between this document and the original file

@@ -14,7 +14,7 @@ to update the original English file first.
 Last Updated: 2007/07/18
 ==================================
 ããã¯ã
-linux-2.6.22-rc4/Documentation/stable_api_nonsense.txt ã®åè¨³
+linux-2.6.22-rc4/Documentation/development-process/stable_api_nonsense.rst ã®åè¨³
 ã§ãã
 ç¿»è¨³å£ä½ï¼ JF ããã¸ã§ã¯ã < http://www.linux.or.jp/JF/ >
 ç¿»è¨³æ¥ ï¼ 2007/06/11

diff --git a/Documentation/ja_JP/stable_kernel_rules.txt b/Documentation/ja_JP/stable_kernel_rules.txt
index 9dbda9b5d21e..b7a201258c76 100644
--- a/Documentation/ja_JP/stable_kernel_rules.txt
+++ b/Documentation/ja_JP/stable_kernel_rules.txt

@@ -1,5 +1,5 @@
 NOTE:
-This is Japanese translated version of "Documentation/stable_kernel_rules.txt".
+This is Japanese translated version of "Documentation/development-process/stable_kernel_rules.rst".
 This one is maintained by Tsugikazu Shibata <tshibata@ab.jp.nec.com>
 and JF Project team <www.linux.or.jp/JF>.
 If you find difference with original file or problem in translation,

@@ -12,7 +12,7 @@ file at first.
 
 ==================================
 ããã¯ã
-linux-2.6.29/Documentation/stable_kernel_rules.txt
+linux-2.6.29/Documentation/development-process/stable_kernel_rules.rst
 ã®åè¨³ã§ãã
 
 ç¿»è¨³å£ä½ï¼ JF ããã¸ã§ã¯ã < http://www.linux.or.jp/JF/ >

@@ -43,7 +43,7 @@ linux-2.6.29/Documentation/stable_kernel_rules.txt
    "çè«çã«ã¯ç«¶åç¶æ

ã«ãªã"ãããªãã®ã¯ä¸å¯ã
  - ãããªãäºç´°ãªä¿®æ£ãå«ãããã¨ã¯ã§ããªãã(ã¹ãã«ã®ä¿®æ£ãç©ºç½ã®ã¯ãªã¼
    ã³ã¢ãããªã©)
- - Documentation/SubmittingPatches ã®è¦åã«å¾ã£ããã®ã§ãªããã°ãªããªãã
+ - Documentation/development-process/SubmittingPatches.rst ã®è¦åã«å¾ã£ããã®ã§ãªããã°ãªããªãã
  - ãããèªä½ãåçã®ä¿®æ£ã Linus ã®ããªã¼ã«æ¢ã«åå¨ããªããã°ãªããªãã
 ã Linus ã®ããªã¼ã§ã®ã³ãããID ã -stable ã¸ã®ãããæç¨¿ã®éã«å¼ç¨ã
    ããã¨ã

diff --git a/Documentation/ko_KR/HOWTO b/Documentation/ko_KR/HOWTO
index 9a3e65924d54..a3f13e62da9e 100644
--- a/Documentation/ko_KR/HOWTO
+++ b/Documentation/ko_KR/HOWTO

@@ -1,5 +1,5 @@
 NOTE:
-This is a version of Documentation/HOWTO translated into korean
+This is a version of Documentation/development-process/HOWTO.rst translated into korean
 This document is maintained by Minchan Kim <minchan@kernel.org>
 If you find any difference between this document and the original file or
 a problem with the translation, please contact the maintainer of this file.

@@ -11,7 +11,7 @@ try to update the original English file first.
 
 ==================================
 ì´ ë¬¸ìë
-Documentation/HOWTO
+Documentation/development-process/HOWTO.rst
 ì íê¸ ë²ìì

ëë¤.
 
 ììï¼ ê¹ë¯¼ì°¬ [off-list ref]

@@ -98,18 +98,18 @@ mtk.manpages@gmail.comì ë©ì¸í

ì´ëìê² ë³´ë¼ ê²ì ê¶ì¥íë¤.
     ë¹ëíê¸° ìí´ íìí ê²ì ì¤ëª
íë¤. ì»¤ëì ì
ë¬¸íë ì¬ëë¤ì ì¬ê¸°ì
     ììí´ì¼ íë¤.
 
-  Documentation/Changes
+  Documentation/development-process/Changes.rst
     ì´ íì¼ì ì»¤ëì ì±ê³µì ì¼ë¡ ë¹ëíê³  ì¤íìí¤ê¸° ìí´ íìí ë¤ìí
     ìíí¸ì¨ì´ í¨í¤ì§ë¤ì ìµì ë²ì ¼ì ëì´íë¤.
 
-  Documentation/CodingStyle
+  Documentation/development-process/CodingStyle.rst
     ì´ ë¬¸ìë ë¦¬ë
ì¤ ì»¤ë ì½ë© ì¤íì¼ê³¼ ê·¸ë ê² í ëªëª ì´ì ë¥¼ ì¤ëª
íë¤.
     ëª¨ë  ìë¡ì´ ì½ëë ì´ ë¬¸ìì ê°ì´ëë¼ì¸ë¤ì ë°ë¼ì¼ íë¤. ëë¶ë¶ì
     ë©ì¸í
ì´ëë¤ì ì´ ê·ì¹ì ë°ë¥´ë í¨ì¹ë¤ë§ì ë°ìë¤ì¼ ê²ì´ê³  ë§ì ì¬ëë¤ì´
     ê·¸ í¨ì¹ê° ì¬ë°ë¥¸ ì¤íì¼ì¼ ê²½ì°ë§ ì½ëë¥¼ ê²í í  ê²ì´ë¤.
 
-  Documentation/SubmittingPatches
-  Documentation/SubmittingDrivers
+  Documentation/development-process/SubmittingPatches.rst
+  Documentation/development-process/SubmittingDrivers.rst
     ì´ íì¼ë¤ì ì±ê³µì ì¼ë¡ í¨ì¹ë¥¼ ë§ë¤ê³  ë³´ë´ë ë²ì ë¤ìì ë´ì©ë¤ë¡
     êµì¥í ìì¸í ì¤ëª
íê³  ìë¤(ê·¸ë¬ë ë¤ìì¼ë¡ íì ëì§ ìëë¤).
        - Email ë´ì©ë¤

@@ -126,7 +126,7 @@ mtk.manpages@gmail.comì ë©ì¸í

ì´ëìê² ë³´ë¼ ê²ì ê¶ì¥íë¤.
     "Linux kernel patch submission format"
         http://linux.yyz.us/patch-format.html
 
-   Documentation/stable_api_nonsense.txt
+   Documentation/development-process/stable_api_nonsense.rst
     ì´ ë¬¸ìë ìëì ì¼ë¡ ì»¤ëì´ ë¶ë³íë APIë¥¼ ê°ì§ ìëë¡ ê²°ì í
     ì´ì ë¥¼ ì¤ëª
íë©° ë¤ìê³¼ ê°ì ê²ë¤ì í¬í¨íë¤.
        - ìë¸ìì¤í
 shim-layer(í¸íì±ì ìí´?)

@@ -136,12 +136,12 @@ mtk.manpages@gmail.comì ë©ì¸í

ì´ëìê² ë³´ë¼ ê²ì ê¶ì¥íë¤.
     ë¦¬ë
ì¤ë¡ ì í¥íë ì¬ëë¤ìê²ë ë§¤ì° ì¤ìíë¤.
 
 
-  Documentation/SecurityBugs
+  Documentation/development-process/SecurityBugs.rst
     ì¬ë¬ë¶ë¤ì´ ë¦¬ë
ì¤ ì»¤ëì ë³´ì ë¬¸ì ë¥¼ ë°ê²¬íë¤ê³  ìê°íë¤ë©´ ì´ ë¬¸ìì
     ëì¨ ë¨ê³ì ë°ë¼ì ì»¤ë ê°ë°ìë¤ìê² ìë¦¬ê³  ê·¸ ë¬¸ì ë¥¼ í´ê²°í  ì ìëë¡
     ëì ë¬ë¼.
 
-  Documentation/ManagementStyle
+  Documentation/development-process/ManagementStyle.rst
     ì´ ë¬¸ìë ë¦¬ë
ì¤ ì»¤ë ë©ì¸í
ì´ëë¤ì´ ê·¸ë¤ì ë°©ë²ë¡ ì ë
¹ì ìë
     ì ì ì ì´ë»ê² ê³µì íê³  ì´ìíëì§ë¥¼ ì¤ëª
íë¤. ì´ê²ì ì»¤ë ê°ë°ì ì
ë¬¸íë
     ëª¨ë  ì¬ëë¤(ëë ì»¤ë ê°ë°ì ìì í¸ê¸°ì¬ì´ë¼ë ìë ì¬ëë¤)ì´

@@ -149,17 +149,17 @@ mtk.manpages@gmail.comì ë©ì¸í

ì´ëìê² ë³´ë¼ ê²ì ê¶ì¥íë¤.
     ë
í¹í íëì ê´íì¬ íí ìë ì¤í´ë¤ê³¼ í¼ëë¤ì í´ìíê³  ìê¸°
     ëë¬¸ì´ë¤.
 
-  Documentation/stable_kernel_rules.txt
+  Documentation/development-process/stable_kernel_rules.rst
     ì´ ë¬¸ìë ìì ì ì¸ ì»¤ë ë°°í¬ê° ì´ë£¨ì´ì§ë ê·ì¹ì ì¤ëª
íê³  ìì¼ë©°
     ì¬ë¬ë¶ë¤ì´ ì´ë¬í ë°°í¬ë¤ ì¤ íëì ë³ê²½ì íê¸¸ ìíë¤ë©´
     ë¬´ìì í´ì¼ íëì§ë¥¼ ì¤ëª
íë¤.
 
-  Documentation/kernel-docs.txt
+  Documentation/development-process/kernel-docs.rst
     ì»¤ë ê°ë°ì ê´ê³ë ì¸ë¶ ë¬¸ìì ë¦¬ì¤í¸ì´ë¤. ì»¤ë ë´ì í¬í¨ë ë¬¸ìë¤
     ì¤ì ì¬ë¬ë¶ì´ ì°¾ê³  ì¶ì ë¬¸ìë¥¼ ë°ê²¬íì§ ëª»í  ê²½ì° ì´ ë¦¬ì¤í¸ë¥¼
     ì´í´ë³´ë¼.
 
-  Documentation/applying-patches.txt
+  Documentation/development-process/applying-patches.rst
     í¨ì¹ê° ë¬´ìì´ë©° ê·¸ê²ì ì»¤ëì ë¤ë¥¸ ê°ë° ë¸ëì¹ë¤ì ì´ë»ê²
     ì ì©íëì§ì ê´íì¬ ìì¸í ì¤ëª
íê³  ìë ì¢ì ì
ë¬¸ìì´ë¤.

@@ -276,7 +276,7 @@ Andrew Mortonì ê¸ì´ ìë¤.
 4.x.yë "stable" í<stable@vger.kernel.org>ì ìí´ ê´ë¦¬ëë©° ê±°ì ë§¤ë² ê²©ì£¼ë¡
 ë°°í¬ëë¤.
 
-ì»¤ë í¸ë¦¬ ë¬¸ìë¤ ë´ì Documentation/stable_kernel_rules.txt íì¼ì ì´ë¤
+ì»¤ë í¸ë¦¬ ë¬¸ìë¤ ë´ì Documentation/development-process/stable_kernel_rules.rst íì¼ì ì´ë¤
 ì¢

ë¥ì ë³ê²½ë¤ì´ -stable í¸ë¦¬ë¡ ë¤ì´ìëì§ì ë°°í¬ íë¡ì¸ì¤ê° ì´ë»ê²
 ì§íëëì§ë¥¼ ì¤ëª
íë¤.

@@ -391,7 +391,7 @@ bugme-janitor ë©ì¼ë§ ë¦¬ì¤í¸(bugzillaì ëª¨ë  ë³íë¤ì´ ì¬ê¸°ì ë©
 "John ì»¤ëí´ì»¤ë ìì±íë¤...."ë¥¼ ì ì§íë©° ì¬ë¬ë¶ë¤ì ìê²¬ì ê·¸ ë©ì¼ì ìë¶ë¶ì
 ìì±íì§ ë§ê³  ê° ì¸ì©í ë¨ë½ë¤ ì¬ì´ì ë£ì´ë¼.
 
-ì¬ë¬ë¶ë¤ì´ í¨ì¹ë¤ì ë©ì¼ì ë£ëë¤ë©´ ê·¸ê²ë¤ì Documentation/SubmittingPatchesì
+ì¬ë¬ë¶ë¤ì´ í¨ì¹ë¤ì ë©ì¼ì ë£ëë¤ë©´ ê·¸ê²ë¤ì Documentation/development-process/SubmittingPatches.rstì
 ëììëë°ë¡ ëª

ë°±í(plain) ì½ì ì ìë í
ì¤í¸ì¬ì¼ íë¤. ì»¤ë ê°ë°ìë¤ì
 ì²¨ë¶íì¼ì´ë ìì¶ë í¨ì¹ë¤ì ìíì§ ìëë¤. ê·¸ë¤ì ì¬ë¬ë¶ë¤ì í¨ì¹ì
 ê° ë¼ì¸ ë¨ìë¡ ì½ë©í¸ë¥¼ íê¸¸ ìíë©° ìì¶íê±°ë ì²¨ë¶íì§ ìê³  ë³´ë´ë ê²ì´

diff --git a/Documentation/ko_KR/stable_api_nonsense.txt b/Documentation/ko_KR/stable_api_nonsense.txt
index 3ba10b11d556..aaf163197ac0 100644
--- a/Documentation/ko_KR/stable_api_nonsense.txt
+++ b/Documentation/ko_KR/stable_api_nonsense.txt

@@ -1,5 +1,5 @@
 NOTE:
-This is a version of Documentation/stable_api_nonsense.txt translated
+This is a version of Documentation/development-process/stable_api_nonsense.rst translated
 into korean
 This document is maintained by Minchan Kim <minchan@kernel.org>
 If you find any difference between this document and the original file or

@@ -12,7 +12,7 @@ try to update the original English file first.
 
 ==================================
 ì´ ë¬¸ìë
-Documentation/stable_api_nonsense.txt
+Documentation/development-process/stable_api_nonsense.rst
 ì íê¸ ë²ìì

ëë¤.
 
 ììï¼ ê¹ë¯¼ì°¬ [off-list ref]

diff --git a/Documentation/networking/PLIP.txt b/Documentation/networking/PLIP.txt
index ad7e3f7c3bbf..0a1e70c39bf2 100644
--- a/Documentation/networking/PLIP.txt
+++ b/Documentation/networking/PLIP.txt

@@ -102,7 +102,7 @@ reason, bits are dropped.
 
 A utility that can perform this change in Linux is plipconfig, which is part
 of the net-tools package (its location can be found in the
-Documentation/Changes file). An example command would be
+Documentation/development-process/Changes.rst file). An example command would be
 'plipconfig plipX trigger 10000', where plipX is the appropriate
 PLIP device.

diff --git a/Documentation/networking/netdev-FAQ.txt b/Documentation/networking/netdev-FAQ.txt
index 0fe1c6e0dbcd..ec20b077f8d1 100644
--- a/Documentation/networking/netdev-FAQ.txt
+++ b/Documentation/networking/netdev-FAQ.txt

@@ -136,14 +136,14 @@ A: Normally Greg Kroah-Hartman collects stable commits himself, but
 
 Q: I see a network patch and I think it should be backported to stable.
    Should I request it via "stable@vger.kernel.org" like the references in
-   the kernel's Documentation/stable_kernel_rules.txt file say?
+   the kernel's Documentation/development-process/stable_kernel_rules.rst file say?
 
 A: No, not for networking.  Check the stable queues as per above 1st to see
    if it is already queued.  If not, then send a mail to netdev, listing
    the upstream commit ID and why you think it should be a stable candidate.
 
    Before you jump to go do the above, do note that the normal stable rules
-   in Documentation/stable_kernel_rules.txt still apply.  So you need to
+   in Documentation/development-process/stable_kernel_rules.rst still apply.  So you need to
    explicitly indicate why it is a critical fix and exactly what users are
    impacted.  In addition, you need to convince yourself that you _really_
    think it has been overlooked, vs. having been considered and rejected.

@@ -165,7 +165,7 @@ A: No.  See above answer.  In short, if you think it really belongs in
 
    If you think there is some valid information relating to it being in
    stable that does _not_ belong in the commit log, then use the three
-   dash marker line as described in Documentation/SubmittingPatches to
+   dash marker line as described in Documentation/development-process/SubmittingPatches.rst to
    temporarily embed that information into the patch that you send.
 
 Q: Someone said that the comment style and coding convention is different

@@ -220,5 +220,5 @@ A: Attention to detail.  Re-read your own work as if you were the
    If it is your first patch, mail it to yourself so you can test apply
    it to an unpatched tree to confirm infrastructure didn't mangle it.
 
-   Finally, go back and read Documentation/SubmittingPatches to be
+   Finally, go back and read Documentation/development-process/SubmittingPatches.rst to be
    sure you are not repeating some common mistake documented there.

diff --git a/Documentation/scsi/scsi_mid_low_api.txt b/Documentation/scsi/scsi_mid_low_api.txt
index 255075157511..1117d4e39d1e 100644
--- a/Documentation/scsi/scsi_mid_low_api.txt
+++ b/Documentation/scsi/scsi_mid_low_api.txt

@@ -336,7 +336,7 @@ in parallel by these functions.
 Conventions
 ===========
 First, Linus Torvalds's thoughts on C coding style can be found in the
-Documentation/CodingStyle file. 
+Documentation/development-process/CodingStyle.rst file. 
 
 Next, there is a movement to "outlaw" typedefs introducing synonyms for 
 struct tags. Both can be still found in the SCSI subsystem, but

diff --git a/Documentation/virtual/kvm/review-checklist.txt b/Documentation/virtual/kvm/review-checklist.txt
index a850986ed684..2446242f366d 100644
--- a/Documentation/virtual/kvm/review-checklist.txt
+++ b/Documentation/virtual/kvm/review-checklist.txt

@@ -1,8 +1,8 @@
 Review checklist for kvm patches
 ================================
 
-1.  The patch must follow Documentation/CodingStyle and
-    Documentation/SubmittingPatches.
+1.  The patch must follow Documentation/development-process/CodingStyle.rst and
+    Documentation/development-process/SubmittingPatches.rst.
 
 2.  Patches should be against kvm.git master branch.

diff --git a/Documentation/watchdog/convert_drivers_to_kernel_api.txt b/Documentation/watchdog/convert_drivers_to_kernel_api.txt
index 271b8850dde7..cad8baa0ce1f 100644
--- a/Documentation/watchdog/convert_drivers_to_kernel_api.txt
+++ b/Documentation/watchdog/convert_drivers_to_kernel_api.txt

@@ -213,6 +213,6 @@ The entry for the driver now needs to select WATCHDOG_CORE:
 Create a patch and send it to upstream
 --------------------------------------
 
-Make sure you understood Documentation/SubmittingPatches and send your patch to
+Make sure you understood Documentation/development-process/SubmittingPatches.rst and send your patch to
 linux-watchdog@vger.kernel.org. We are looking forward to it :)

diff --git a/Documentation/zh_CN/CodingStyle b/Documentation/zh_CN/CodingStyle
index 12717791baac..cc9645d19ba3 100644
--- a/Documentation/zh_CN/CodingStyle
+++ b/Documentation/zh_CN/CodingStyle

@@ -1,4 +1,4 @@
-Chinese translated version of Documentation/CodingStyle
+Chinese translated version of Documentation/development-process/CodingStyle.rst
 
 If you have any comment or update to the content, please post to LKML directly.
 However, if you have problem communicating in English you can also ask the

@@ -7,7 +7,7 @@ translation is outdated or there is problem with translation.
 
 Chinese maintainer: Zhang Le <r0bertz@gentoo.org>
 ---------------------------------------------------------------------
-Documentation/CodingStyleçä¸æç¿»è¯
+Documentation/development-process/CodingStyle.rstçä¸æç¿»è¯
 
 å¦ææ³è¯è®ºææ´æ°æ¬æçå

å®¹ï¼è¯·ç´æ¥åä¿¡å°LKMLãå¦æä½ ä½¿ç¨è±æäº¤æµæå°é¾çè¯ï¼ä¹å¯
 ä»¥åä¸æçç»´æ¤è
æ±å©ãå¦ææ¬ç¿»è¯æ´æ°ä¸åæ¶æè
ç¿»è¯åå¨é®é¢ï¼è¯·èç³»ä¸æçç»´æ¤è
ã

diff --git a/Documentation/zh_CN/HOWTO b/Documentation/zh_CN/HOWTO
index f0613b92e0be..6d6fe1209b71 100644
--- a/Documentation/zh_CN/HOWTO
+++ b/Documentation/zh_CN/HOWTO

@@ -1,4 +1,4 @@
-ï»¿Chinese translated version of Documentation/HOWTO
+ï»¿Chinese translated version of Documentation/development-process/HOWTO.rst
 
 If you have any comment or update to the content, please contact the
 original document maintainer directly.  However, if you have a problem

@@ -9,7 +9,7 @@ or if there is a problem with the translation.
 Maintainer: Greg Kroah-Hartman <greg@kroah.com>
 Chinese maintainer: Li Yang <leoli@freescale.com>
 ---------------------------------------------------------------------
-Documentation/HOWTO çä¸æç¿»è¯
+Documentation/development-process/HOWTO.rst çä¸æç¿»è¯
 
 å¦ææ³è¯è®ºææ´æ°æ¬æçå

å®¹ï¼è¯·ç´æ¥èç³»åææ¡£çç»´æ¤è
ãå¦æä½ ä½¿ç¨è±æ
 äº¤æµæå°é¾çè¯ï¼ä¹å¯ä»¥åä¸æçç»´æ¤è
æ±å©ãå¦ææ¬ç¿»è¯æ´æ°ä¸åæ¶æè
ç¿»

@@ -93,16 +93,16 @@ Linuxå

æ ¸ä»£ç ä¸å
å«æå¤§éçææ¡£ãè¿äºææ¡£å¯¹äºå¦ä¹ å¦ä½ä¸
     æä»¶ç®è¦ä»ç»äºLinuxå
æ ¸çèæ¯ï¼å¹¶ä¸æè¿°äºå¦ä½é
ç½®åç¼è¯å
æ ¸ãå
æ ¸ç
     æ°ç¨æ·åºè¯¥ä»è¿éå¼å§ã
 
-  Documentation/Changes
+  Documentation/development-process/Changes.rst
     æä»¶ç»åºäºç¨æ¥ç¼è¯åä½¿ç¨å
æ ¸æéè¦çæå°è½¯ä»¶å
åè¡¨ã
 
-  Documentation/CodingStyle
+  Documentation/development-process/CodingStyle.rst
     æè¿°Linuxå
æ ¸çä»£ç é£æ ¼åçç±ãæææ°ä»£ç éè¦éµå®è¿ç¯ææ¡£ä¸å®ä¹çè§
     èãå¤§å¤æ°ç»´æ¤è
åªä¼æ¥æ¶ç¬¦åè§å®çè¡¥ä¸ï¼å¾å¤äººä¹åªä¼å¸®å¿æ£æ¥ç¬¦åé£æ ¼
     çä»£ç ã
 
-  Documentation/SubmittingPatches
-  Documentation/SubmittingDrivers
+  Documentation/development-process/SubmittingPatches.rst
+  Documentation/development-process/SubmittingDrivers.rst
     è¿ä¸¤ä»½ææ¡£æç¡®æè¿°å¦ä½åå»ºååéè¡¥ä¸ï¼å
¶ä¸å
æ¬ï¼ä½ä¸ä»
éäº)ï¼
        - é®ä»¶å
å®¹
        - é®ä»¶æ ¼å¼

@@ -116,7 +116,7 @@ Linuxå

æ ¸ä»£ç ä¸å
å«æå¤§éçææ¡£ãè¿äºææ¡£å¯¹äºå¦ä¹ å¦ä½ä¸
     "Linux kernel patch submission format"
         http://linux.yyz.us/patch-format.html
 
-  Documentation/stable_api_nonsense.txt
+  Documentation/development-process/stable_api_nonsense.rst
     è®ºè¯å
æ ¸ä¸ºä»ä¹ç¹æä¸å
æ¬ç¨³å®çå
æ ¸å
é¨APIï¼ä¹å°±æ¯è¯´ä¸å
æ¬åè¿æ ·çç¹
     æ§ï¼
        - åç³»ç»ä¸é´å±ï¼ä¸ºäºå
¼å®¹æ§ï¼ï¼

@@ -125,23 +125,23 @@ Linuxå

æ ¸ä»£ç ä¸å
å«æå¤§éçææ¡£ãè¿äºææ¡£å¯¹äºå¦ä¹ å¦ä½ä¸
     è¿ç¯ææ¡£å¯¹äºçè§£Linuxçå¼åå²å¦è³å
³éè¦ãå¯¹äºå°å¼åå¹³å°ä»å
¶ä»æä½ç³»
     ç»è½¬ç§»å°Linuxçäººæ¥è¯´ä¹å¾éè¦ã
 
-  Documentation/SecurityBugs
+  Documentation/development-process/SecurityBugs.rst
     å¦æä½ è®¤ä¸ºèªå·±åç°äºLinuxå
æ ¸çå®å
¨æ§é®é¢ï¼è¯·æ ¹æ®è¿ç¯ææ¡£ä¸çæ¥éª¤æ¥
     æéå
¶ä»å
æ ¸å¼åè
å¹¶å¸®å©è§£å³è¿ä¸ªé®é¢ã
 
-  Documentation/ManagementStyle
+  Documentation/development-process/ManagementStyle.rst
     æè¿°å
æ ¸ç»´æ¤è
çå·¥ä½æ¹æ³åå
¶å
±æç¹ç¹ãè¿å¯¹äºååæ¥è§¦å
æ ¸å¼åï¼æè
å¯¹
     å®æå°å¥½å¥ï¼çäººæ¥è¯´å¾éè¦ï¼å ä¸ºå®è§£éäºå¾å¤å¯¹äºå
æ ¸ç»´æ¤è
ç¬ç¹è¡ä¸ºç
     æ®éè¯¯è§£ä¸è¿·æã
 
-  Documentation/stable_kernel_rules.txt
+  Documentation/development-process/stable_kernel_rules.rst
     è§£éäºç¨³å®çå
æ ¸åå¸çè§åï¼ä»¥åå¦ä½å°æ¹å¨æ¾å
¥è¿äºçæ¬çæ¥éª¤ã
 
-  Documentation/kernel-docs.txt
+  Documentation/development-process/kernel-docs.rst
     æå©äºå
æ ¸å¼åçå¤é¨ææ¡£åè¡¨ãå¦æä½ å¨å
æ ¸èªå¸¦çææ¡£ä¸æ²¡ææ¾å°ä½ æ³æ¾
     çå
å®¹ï¼å¯ä»¥æ¥çè¿äºææ¡£ã
 
-  Documentation/applying-patches.txt
+  Documentation/development-process/applying-patches.rst
     å
³äºè¡¥ä¸æ¯ä»ä¹ä»¥åå¦ä½å°å®æå¨ä¸åå
æ ¸å¼ååæ¯ä¸çå¥½ä»ç»
 
 å
æ ¸è¿æ¥æå¤§éä»ä»£ç èªå¨çæçææ¡£ãå®å
å«å
æ ¸å
é¨APIçå
¨é¢ä»ç»ä»¥åå¦ä½

@@ -238,7 +238,7 @@ kernel.orgç½ç«çpub/linux/kernel/v2.6/ç®å½ä¸æ¾å°å®ãå®çå¼åéµå¾ª
 2.6.x.yçæ¬ç±âç¨³å®çâå°ç»ï¼é®ä»¶å°å<stable@vger.kernel.org>ï¼ç»´æ¤ï¼ä¸è¬éå¨å
 å¸æ°çæ¬ã
 
-å

æ ¸æºç ä¸çDocumentation/stable_kernel_rules.txtæä»¶å
·ä½æè¿°äºå¯è¢«ç¨³å®
+å
æ ¸æºç ä¸çDocumentation/development-process/stable_kernel_rules.rstæä»¶å
·ä½æè¿°äºå¯è¢«ç¨³å®
 çå
æ ¸æ¥åçä¿®æ¹ç±»åä»¥ååå¸çæµç¨ã

@@ -380,7 +380,7 @@ MAINTAINERSæä»¶ä¸­å¯ä»¥æ¾å°ä¸åè¯é¢å¯¹åºçé®ä»¶åè¡¨ã
 è¿å è¡ãå°ä½ çè¯è®ºå å¨è¢«å¼ç¨çæ®µè½ä¹é´èä¸è¦æ¾å¨é®ä»¶çé¡¶é¨ã
 
 å¦æä½ å¨é®ä»¶ä¸­éå¸¦è¡¥ä¸ï¼è¯·ç¡®è®¤å®ä»¬æ¯å¯ä»¥ç´æ¥é

è¯»ççº¯ææ¬ï¼å¦
-Documentation/SubmittingPatchesææ¡£ä¸æè¿°ï¼ãå
æ ¸å¼åè
ä»¬ä¸å¸æéå°éä»¶
+Documentation/development-process/SubmittingPatches.rstææ¡£ä¸æè¿°ï¼ãå
æ ¸å¼åè
ä»¬ä¸å¸æéå°éä»¶
 æè
è¢«åç¼©äºçè¡¥ä¸ãåªæè¿æ ·æè½ä¿è¯ä»ä»¬å¯ä»¥ç´æ¥è¯è®ºä½ çæ¯è¡ä»£ç ãè¯·ç¡®ä¿
 ä½ ä½¿ç¨çé®ä»¶åéç¨åºä¸ä¼ä¿®æ¹ç©ºæ ¼åå¶è¡¨ç¬¦ãä¸ä¸ªé²èæ§çæµè¯æ¹æ³æ¯å
å°é®ä»¶
 åéç»èªå·±ï¼ç¶åèªå·±å°è¯æ¯å¦å¯ä»¥é¡ºå©å°æä¸æ¶å°çè¡¥ä¸ãå¦ææµè¯ä¸æåï¼è¯·

diff --git a/Documentation/zh_CN/SecurityBugs b/Documentation/zh_CN/SecurityBugs
index d21eb07fe943..8b1a0af493e1 100644
--- a/Documentation/zh_CN/SecurityBugs
+++ b/Documentation/zh_CN/SecurityBugs

@@ -1,4 +1,4 @@
-Chinese translated version of Documentation/SecurityBugs
+Chinese translated version of Documentation/development-process/SecurityBugs.rst
 
 If you have any comment or update to the content, please contact the
 original document maintainer directly.  However, if you have a problem

@@ -8,7 +8,7 @@ or if there is a problem with the translation.
 
 Chinese maintainer: Harry Wei <harryxiyou@gmail.com>
 ---------------------------------------------------------------------
-Documentation/SecurityBugs çä¸æç¿»è¯
+Documentation/development-process/SecurityBugs.rst çä¸æç¿»è¯
 
 å¦ææ³è¯è®ºææ´æ°æ¬æçå

å®¹ï¼è¯·ç´æ¥èç³»åææ¡£çç»´æ¤è
ãå¦æä½ ä½¿ç¨è±æ
 äº¤æµæå°é¾çè¯ï¼ä¹å¯ä»¥åä¸æçç»´æ¤è
æ±å©ãå¦ææ¬ç¿»è¯æ´æ°ä¸åæ¶æè
ç¿»

diff --git a/Documentation/zh_CN/SubmittingDrivers b/Documentation/zh_CN/SubmittingDrivers
index d313f5d8448d..b59caa9e8ac8 100644
--- a/Documentation/zh_CN/SubmittingDrivers
+++ b/Documentation/zh_CN/SubmittingDrivers

@@ -1,4 +1,4 @@
-ï»¿Chinese translated version of Documentation/SubmittingDrivers
+ï»¿Chinese translated version of Documentation/development-process/SubmittingDrivers.rst
 
 If you have any comment or update to the content, please contact the
 original document maintainer directly.  However, if you have a problem

@@ -8,7 +8,7 @@ or if there is a problem with the translation.
 
 Chinese maintainer: Li Yang <leo@zh-kernel.org>
 ---------------------------------------------------------------------
-Documentation/SubmittingDrivers çä¸æç¿»è¯
+Documentation/development-process/SubmittingDrivers.rst çä¸æç¿»è¯
 
 å¦ææ³è¯è®ºææ´æ°æ¬æçå

å®¹ï¼è¯·ç´æ¥èç³»åææ¡£çç»´æ¤è
ãå¦æä½ ä½¿ç¨è±æ
 äº¤æµæå°é¾çè¯ï¼ä¹å¯ä»¥åä¸æçç»´æ¤è
æ±å©ãå¦ææ¬ç¿»è¯æ´æ°ä¸åæ¶æè
ç¿»

@@ -30,7 +30,7 @@ Documentation/SubmittingDrivers çä¸­æç¿»è¯
 å

´è¶£çæ¯æ¾å¡é©±å¨ç¨åºï¼ä½ ä¹è®¸åºè¯¥è®¿é® XFree86 é¡¹ç®(http://www.xfree86.org/)
 åï¼æ X.org é¡¹ç® (http://x.org)ã
 
-å¦è¯·åé
 Documentation/SubmittingPatches ææ¡£ã
+å¦è¯·åé
 Documentation/development-process/SubmittingPatches.rst ææ¡£ã
 
 
 åé
è®¾å¤å·

@@ -81,7 +81,7 @@ Linux 2.6:
 		å¦æä½ éè¦ä¸ä¸ª Linux å NT çéç¨é©±å¨æ¥å£ï¼é£ä¹è¯·å¨ç¨
 		æ·ç©ºé´å®ç°å®ã
 
-ä»£ç ï¼		è¯·ä½¿ç¨ Documentation/CodingStyle ä¸­ææè¿°ç Linux ä»£ç é£
+ä»£ç ï¼		è¯·ä½¿ç¨ Documentation/development-process/CodingStyle.rst ä¸­ææè¿°ç Linux ä»£ç é£
 		æ ¼ãå¦æä½ çæäºä»£ç æ®µï¼ä¾å¦é£äºä¸ Windows é©±å¨ç¨åºå

å
±
 		äº«çä»£ç æ®µï¼éè¦ä½¿ç¨å
¶ä»æ ¼å¼ï¼èä½ å´åªå¸æç»´æ¤ä¸ä»½ä»£ç ï¼
 		é£ä¹è¯·å°å®ä»¬å¾å¥½å°åºååºæ¥ï¼å¹¶ä¸æ³¨æåå ã

diff --git a/Documentation/zh_CN/SubmittingPatches b/Documentation/zh_CN/SubmittingPatches
index 1d3a10f8746b..8b93acb3a75e 100644
--- a/Documentation/zh_CN/SubmittingPatches
+++ b/Documentation/zh_CN/SubmittingPatches

@@ -1,4 +1,4 @@
-Chinese translated version of Documentation/SubmittingPatches
+Chinese translated version of Documentation/development-process/SubmittingPatches.rst
 
 If you have any comment or update to the content, please contact the
 original document maintainer directly.  However, if you have a problem

@@ -8,7 +8,7 @@ or if there is a problem with the translation.
 
 Chinese maintainer: TripleX Chung <triplex@zh-kernel.org>
 ---------------------------------------------------------------------
-Documentation/SubmittingPatches çä¸æç¿»è¯
+Documentation/development-process/SubmittingPatches.rst çä¸æç¿»è¯
 
 å¦ææ³è¯è®ºææ´æ°æ¬æçå

å®¹ï¼è¯·ç´æ¥èç³»åææ¡£çç»´æ¤è
ãå¦æä½ ä½¿ç¨è±æ
 äº¤æµæå°é¾çè¯ï¼ä¹å¯ä»¥åä¸æçç»´æ¤è
æ±å©ãå¦ææ¬ç¿»è¯æ´æ°ä¸åæ¶æè
ç¿»

@@ -32,7 +32,7 @@ Documentation/SubmittingPatches çä¸­æç¿»è¯
 çæ¹å¨è¢«æ¥åçæºä¼ã
 é

è¯» Documentation/SubmitChecklist æ¥è·å¾å¨æäº¤ä»£ç åéè¦æ£æ¥çé¡¹ç®çå
 è¡¨ãå¦æä½ å¨æäº¤ä¸ä¸ªé©±å¨ç¨åºï¼é£ä¹åæ¶é
è¯»ä¸ä¸
-Documentation/SubmittingDrivers ã
+Documentation/development-process/SubmittingDrivers.rst ã
 
 
 --------------------------

@@ -404,8 +404,8 @@ Greg Kroah-Hartman, "How to piss off a kernel subsystem maintainer".
 NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!
   <https://lkml.org/lkml/2005/7/11/336>
 
-Kernel Documentation/CodingStyle:
-  <http://sosdg.org/~coywolf/lxr/source/Documentation/CodingStyle>
+Kernel Documentation/development-process/CodingStyle.rst:
+  <http://sosdg.org/~coywolf/lxr/source/Documentation/development-process/CodingStyle.rst>
 
 Linus Torvalds's mail on the canonical patch format:
   <http://lkml.org/lkml/2005/4/7/183>

diff --git a/Documentation/zh_CN/stable_api_nonsense.txt b/Documentation/zh_CN/stable_api_nonsense.txt
index c26a27d1ee7d..5f37f56ab7ec 100644
--- a/Documentation/zh_CN/stable_api_nonsense.txt
+++ b/Documentation/zh_CN/stable_api_nonsense.txt

@@ -1,4 +1,4 @@
-Chinese translated version of Documentation/stable_api_nonsense.txt
+Chinese translated version of Documentation/development-process/stable_api_nonsense.rst
 
 If you have any comment or update to the content, please contact the
 original document maintainer directly.  However, if you have problem

@@ -9,7 +9,7 @@ is problem with translation.
 Maintainer: Greg Kroah-Hartman <greg@kroah.com>
 Chinese maintainer: TripleX Chung <zhongyu@18mail.cn>
 ---------------------------------------------------------------------
-Documentation/stable_api_nonsense.txt çä¸æç¿»è¯
+Documentation/development-process/stable_api_nonsense.rst çä¸æç¿»è¯
 
 å¦ææ³è¯è®ºææ´æ°æ¬æçå

å®¹ï¼è¯·ç´æ¥èç³»åææ¡£çç»´æ¤è
ãå¦æä½ ä½¿ç¨è±æ
 äº¤æµæå°é¾çè¯ï¼ä¹å¯ä»¥åä¸æçç»´æ¤è
æ±å©ãå¦ææ¬ç¿»è¯æ´æ°ä¸åæ¶æè
ç¿»

diff --git a/Documentation/zh_CN/stable_kernel_rules.txt b/Documentation/zh_CN/stable_kernel_rules.txt
index 26ea5ed7cd9c..e8e09a9a1891 100644
--- a/Documentation/zh_CN/stable_kernel_rules.txt
+++ b/Documentation/zh_CN/stable_kernel_rules.txt

@@ -1,4 +1,4 @@
-Chinese translated version of Documentation/stable_kernel_rules.txt
+Chinese translated version of Documentation/development-process/stable_kernel_rules.rst
 
 If you have any comment or update to the content, please contact the
 original document maintainer directly.  However, if you have a problem

@@ -8,7 +8,7 @@ or if there is a problem with the translation.
 
 Chinese maintainer: TripleX Chung <triplex@zh-kernel.org>
 ---------------------------------------------------------------------
-Documentation/stable_kernel_rules.txt çä¸æç¿»è¯
+Documentation/development-process/stable_kernel_rules.rst çä¸æç¿»è¯
 
 å¦ææ³è¯è®ºææ´æ°æ¬æçå

å®¹ï¼è¯·ç´æ¥èç³»åææ¡£çç»´æ¤è
ãå¦æä½ ä½¿ç¨è±æ
 äº¤æµæå°é¾çè¯ï¼ä¹å¯ä»¥åä¸æçç»´æ¤è
æ±å©ãå¦ææ¬ç¿»è¯æ´æ°ä¸åæ¶æè
ç¿»

@@ -38,7 +38,7 @@ Documentation/stable_kernel_rules.txt çä¸­æç¿»è¯
   - æ²¡æâçè®ºä¸çç«äºæ¡ä»¶âï¼é¤éè½ç»åºç«äºæ¡ä»¶å¦ä½è¢«å©ç¨çè§£éã
   - ä¸è½å­å¨ä»»ä½çâçç¢çâä¿®æ­£ï¼æ¼åä¿®æ­£ï¼å»æå¤ä½ç©ºæ ¼ä¹ç±»çï¼ã
   - å¿

é¡»è¢«ç¸å
³åç³»ç»çç»´æ¤è
æ¥åã
-  - å¿
é¡»éµå¾ªDocumentation/SubmittingPatcheséçè§åã
+  - å¿
é¡»éµå¾ªDocumentation/development-process/SubmittingPatches.rstéçè§åã
 
 åç¨³å®çä»£ç æ æäº¤è¡¥ä¸çè¿ç¨ï¼

diff --git a/MAINTAINERS b/MAINTAINERS
index 9c4469949f28..5c64195f00ee 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS

@@ -35,7 +35,7 @@ trivial patch so apply some common sense.
 
 	PLEASE check your patch with the automated style checker
 	(scripts/checkpatch.pl) to catch trivial style violations.
-	See Documentation/CodingStyle for guidance here.
+	See Documentation/development-process/CodingStyle.rst for guidance here.
 
 	PLEASE CC: the maintainers and mailing lists that are generated
 	by scripts/get_maintainer.pl.  The results returned by the

diff --git a/README b/README
index 09f34f78f2bb..0a5a8d862021 100644
--- a/README
+++ b/README

@@ -114,7 +114,7 @@ SOFTWARE REQUIREMENTS
 
    Compiling and running the 4.x kernels requires up-to-date
    versions of various software packages.  Consult
-   Documentation/Changes for the minimum version numbers required
+   Documentation/development-process/Changes.rst for the minimum version numbers required
    and how to get updates for these packages.  Beware that using
    excessively old versions of these packages can cause indirect
    errors that are very difficult to track down, so don't assume that

@@ -245,7 +245,7 @@ CONFIGURING the kernel:
 COMPILING the kernel:
 
  - Make sure you have at least gcc 3.2 available.
-   For more information, refer to Documentation/Changes.
+   For more information, refer to Documentation/development-process/Changes.rst.
 
    Please note that you can still run a.out user programs with this kernel.

diff --git a/REPORTING-BUGS b/REPORTING-BUGS
index 914baf9cf5fa..853c264bd092 100644
--- a/REPORTING-BUGS
+++ b/REPORTING-BUGS

@@ -55,7 +55,7 @@ files to the get_maintainer.pl script:
 
 If it is a security bug, please copy the Security Contact listed in the
 MAINTAINERS file.  They can help coordinate bugfix and disclosure.  See
-Documentation/SecurityBugs for more information.
+Documentation/development-process/SecurityBugs.rst for more information.
 
 If you can't figure out which subsystem caused the issue, you should file
 a bug in kernel.org bugzilla and send email to

diff --git a/drivers/net/ppp/Kconfig b/drivers/net/ppp/Kconfig
index 1373c6d7278d..49c93a693b67 100644
--- a/drivers/net/ppp/Kconfig
+++ b/drivers/net/ppp/Kconfig

@@ -15,7 +15,7 @@ config PPP
 	  To use PPP, you need an additional program called pppd as described
 	  in the PPP-HOWTO, available at
 	  <http://www.tldp.org/docs.html#howto>.  Make sure that you have
-	  the version of pppd recommended in <file:Documentation/Changes>.
+	  the version of pppd recommended in <file:Documentation/development-process/Changes.rst>.
 	  The PPP option enlarges your kernel by about 16 KB.
 
 	  There are actually two versions of PPP: the traditional PPP for

diff --git a/drivers/pcmcia/Kconfig b/drivers/pcmcia/Kconfig
index d3c378b4db6c..b8ef9e674a49 100644
--- a/drivers/pcmcia/Kconfig
+++ b/drivers/pcmcia/Kconfig

@@ -26,7 +26,7 @@ config PCMCIA
 	   only using 32-bit CardBus cards, say Y or M here.
 
 	   To use 16-bit PCMCIA cards, you will need supporting software in
-	   most cases. (see the file <file:Documentation/Changes> for
+	   most cases. (see the file <file:Documentation/development-process/Changes.rst> for
 	   location and details).
 
 	   To compile this driver as modules, choose M here: the

diff --git a/fs/Kconfig.binfmt b/fs/Kconfig.binfmt
index c7efddf6e038..aba0e09a0053 100644
--- a/fs/Kconfig.binfmt
+++ b/fs/Kconfig.binfmt

@@ -21,7 +21,7 @@ config BINFMT_ELF
 	  If you find that after upgrading from Linux kernel 1.2 and saying Y
 	  here, you still can't run any ELF binaries (they just crash), then
 	  you'll have to install the newest ELF runtime libraries, including
-	  ld.so (check the file <file:Documentation/Changes> for location and
+	  ld.so (check the file <file:Documentation/development-process/Changes.rst> for location and
 	  latest version).
 
 config COMPAT_BINFMT_ELF

diff --git a/fs/fuse/Kconfig b/fs/fuse/Kconfig
index 1b2f6c2c3aaf..f55c3596c21e 100644
--- a/fs/fuse/Kconfig
+++ b/fs/fuse/Kconfig

@@ -11,7 +11,7 @@ config FUSE_FS
 	  installed if you've installed the "fuse" package itself.
 
 	  See <file:Documentation/filesystems/fuse.txt> for more information.
-	  See <file:Documentation/Changes> for needed library/utility version.
+	  See <file:Documentation/development-process/Changes.rst> for needed library/utility version.
 
 	  If you want to develop a userspace FS, or if you want to use
 	  a filesystem based on FUSE, answer Y or M.

diff --git a/net/Kconfig b/net/Kconfig
index c2cdbce629bd..71edecbb7ee9 100644
--- a/net/Kconfig
+++ b/net/Kconfig

@@ -17,7 +17,7 @@ menuconfig NET
 	  should consider updating your networking tools too because changes
 	  in the kernel and the tools often go hand in hand. The tools are
 	  contained in the package net-tools, the location and version number
-	  of which are given in <file:Documentation/Changes>.
+	  of which are given in <file:Documentation/development-process/Changes.rst>.
 
 	  For a general introduction to Linux networking, it is highly
 	  recommended to read the NET-HOWTO, available from

@@ -159,7 +159,7 @@ menuconfig NETFILTER
 	  Various modules exist for netfilter which replace the previous
 	  masquerading (ipmasqadm), packet filtering (ipchains), transparent
 	  proxying, and portforwarding mechanisms. Please see
-	  <file:Documentation/Changes> under "iptables" for the location of
+	  <file:Documentation/development-process/Changes.rst> under "iptables" for the location of
 	  these packages.
 
 if NETFILTER

diff --git a/scripts/ver_linux b/scripts/ver_linux
index 0d8bd29b1bd6..931e933c4bcf 100755
--- a/scripts/ver_linux
+++ b/scripts/ver_linux

@@ -5,7 +5,7 @@
 # differ on your system.
 #
 echo 'If some fields are empty or look unusual you may have an old version.'
-echo 'Compare to the current minimal requirements in Documentation/Changes.'
+echo 'Compare to the current minimal requirements in Documentation/development-process/Changes.rst.'
 echo ' '
 
 uname -a

diff --git a/tools/testing/selftests/futex/README b/tools/testing/selftests/futex/README
index 0558bb9ce0a6..5253e7efd120 100644
--- a/tools/testing/selftests/futex/README
+++ b/tools/testing/selftests/futex/README

@@ -59,4 +59,4 @@ o FIXME: decide on a sane test naming scheme.  Currently the tests are named
 Coding Style
 ------------
 o The Futex Test project adheres to the coding standards set forth by Linux
-  kernel as defined in the Linux source Documentation/CodingStyle.
+  kernel as defined in the Linux source Documentation/development-process/CodingStyle.rst.

-- 
2.7.4

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help