From: Jonathan Corbet <corbet@lwn.net>
To: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Vineet Gupta <vgupta@kernel.org>
Subject: [PATCH 1/4] docs: Move arc architecture docs under Documentation/arch/
Date: Thu, 30 Mar 2023 13:56:01 -0600 [thread overview]
Message-ID: <20230330195604.269346-2-corbet@lwn.net> (raw)
In-Reply-To: <20230330195604.269346-1-corbet@lwn.net>
Architecture-specific documentation is being moved into Documentation/arch/
as a way of cleaning up the top-level documentation directory and making
the docs hierarchy more closely match the source hierarchy. Move
Documentation/arc into arch/ and fix all in-tree references.
Cc: Vineet Gupta <vgupta@kernel.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
---
Documentation/{ => arch}/arc/arc.rst | 0
Documentation/{ => arch}/arc/features.rst | 0
Documentation/{ => arch}/arc/index.rst | 0
Documentation/arch/index.rst | 2 +-
MAINTAINERS | 2 +-
5 files changed, 2 insertions(+), 2 deletions(-)
rename Documentation/{ => arch}/arc/arc.rst (100%)
rename Documentation/{ => arch}/arc/features.rst (100%)
rename Documentation/{ => arch}/arc/index.rst (100%)
diff --git a/Documentation/arc/arc.rst b/Documentation/arch/arc/arc.rst
similarity index 100%
rename from Documentation/arc/arc.rst
rename to Documentation/arch/arc/arc.rst
diff --git a/Documentation/arc/features.rst b/Documentation/arch/arc/features.rst
similarity index 100%
rename from Documentation/arc/features.rst
rename to Documentation/arch/arc/features.rst
diff --git a/Documentation/arc/index.rst b/Documentation/arch/arc/index.rst
similarity index 100%
rename from Documentation/arc/index.rst
rename to Documentation/arch/arc/index.rst
diff --git a/Documentation/arch/index.rst b/Documentation/arch/index.rst
index ccb4d10fc1b6..2aeff47a0014 100644
--- a/Documentation/arch/index.rst
+++ b/Documentation/arch/index.rst
@@ -9,7 +9,7 @@ implementation.
.. toctree::
:maxdepth: 2
- ../arc/index
+ arc/index
../arm/index
../arm64/index
../ia64/index
diff --git a/MAINTAINERS b/MAINTAINERS
index 64ea94536f4c..78ff43f63753 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20185,7 +20185,7 @@ M: Vineet Gupta <vgupta@kernel.org>
L: linux-snps-arc@lists.infradead.org
S: Supported
T: git git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git
-F: Documentation/arc/
+F: Documentation/arch/arc
F: Documentation/devicetree/bindings/arc/*
F: Documentation/devicetree/bindings/interrupt-controller/snps,arc*
F: arch/arc/
--
2.39.2
next prev parent reply other threads:[~2023-03-30 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 19:56 [PATCH 0/4] docs: move yet more architecture docs Jonathan Corbet
2023-03-30 19:56 ` Jonathan Corbet [this message]
2023-04-02 6:44 ` [PATCH 1/4] docs: Move arc architecture docs under Documentation/arch/ Vineet Gupta
2023-03-30 19:56 ` [PATCH 2/4] docs: move ia64 " Jonathan Corbet
2023-03-30 19:56 ` [PATCH 3/4] docs: move parisc documentation " Jonathan Corbet
2023-04-01 6:43 ` Yanteng Si
2023-03-30 19:56 ` [PATCH 4/4] docs: move m68k architecture " Jonathan Corbet
2023-03-31 7:44 ` Geert Uytterhoeven
2023-03-31 13:02 ` Jonathan Corbet
2023-03-31 13:03 ` Jonathan Corbet
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=20230330195604.269346-2-corbet@lwn.net \
--to=corbet@lwn.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgupta@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