From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Costa Shulyupin" <costa.shul@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Federico Vaga" <federico.vaga@vaga.pv.it>,
"Alex Shi" <alexs@kernel.org>,
"Yanteng Si" <siyanteng@loongson.cn>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Atish Patra" <atishp@rivosinc.com>,
"Alexandre Ghiti" <alexghiti@rivosinc.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Andrew Jones" <ajones@ventanamicro.com>,
"Evan Green" <evan@rivosinc.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Heiko Stuebner" <heiko@sntech.de>,
"Andy Chiu" <andy.chiu@sifive.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Greentime Hu" <greentime.hu@sifive.com>,
"Anup Patel" <anup@brainfault.org>,
"Charlie Jenkins" <charlie@rivosinc.com>,
"Vincent Chen" <vincent.chen@sifive.com>,
"Wu XiangCheng" <bobwxc@email.cn>,
"Sami Tolvanen" <samitolvanen@google.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, workflows@vger.kernel.org
Subject: Re: [PATCH] docs: move riscv under arch
Date: Thu, 28 Sep 2023 17:58:16 +0700 [thread overview]
Message-ID: <ZRVcSDkMmWaePqaL@debian.me> (raw)
In-Reply-To: <20230928103134.2779459-1-costa.shul@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On Thu, Sep 28, 2023 at 01:29:42PM +0300, Costa Shulyupin wrote:
> and fix all in-tree references.
>
> 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.
>
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-09-28 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 10:29 Costa Shulyupin
2023-09-28 10:58 ` Bagas Sanjaya [this message]
2023-09-30 9:06 ` Conor Dooley
2023-09-30 14:26 ` Jonathan Corbet
2023-09-30 18:52 ` [PATCH v1] " Costa Shulyupin
2023-10-02 13:25 ` Conor Dooley
2023-10-10 19:47 ` Jonathan Corbet
2023-11-12 0:55 ` patchwork-bot+linux-riscv
2023-10-02 13:15 ` [PATCH] " Conor Dooley
2023-10-02 15:32 ` 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=ZRVcSDkMmWaePqaL@debian.me \
--to=bagasdotme@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=alexs@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=atishp@rivosinc.com \
--cc=bhelgaas@google.com \
--cc=bjorn@rivosinc.com \
--cc=bobwxc@email.cn \
--cc=charlie@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=evan@rivosinc.com \
--cc=federico.vaga@vaga.pv.it \
--cc=greentime.hu@sifive.com \
--cc=hca@linux.ibm.com \
--cc=heiko@sntech.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=philmd@linaro.org \
--cc=rdunlap@infradead.org \
--cc=samitolvanen@google.com \
--cc=siyanteng@loongson.cn \
--cc=vincent.chen@sifive.com \
--cc=workflows@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