From: Jonathan Corbet <corbet@lwn.net>
To: "Alexandre Ghiti" <alex@ghiti.fr>,
"Alexandre Ghiti" <alexghiti@rivosinc.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Andrew Jones" <ajones@ventanamicro.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Sunil V L" <sunilvl@ventanamicro.com>,
"Song Shuai" <songshuaishuai@tinylab.org>,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Atish Patra <atishp@rivosinc.com>
Subject: Re: [PATCH v4 1/3] Documentation: arm: Add bootargs to the table of added DT parameters
Date: Sat, 22 Jul 2023 13:00:28 -0600 [thread overview]
Message-ID: <871qgzbwkz.fsf@meer.lwn.net> (raw)
In-Reply-To: <d8db4fc3-12b4-43f1-ea94-5dc53ce2d55f@ghiti.fr>
Alexandre Ghiti <alex@ghiti.fr> writes:
>> In the former case, they don't apply to docs-next, so could I get a
>> respin please?
>
> Yes sure, I'll do that now. BTW all the arch documentation was moved in
> Documentation/arch/, but not the riscv, are you working on this or
> should we?
I'll get there - unless somebody beats me to it :)
Thanks,
jon
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-07-22 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 14:36 [PATCH v4 1/3] Documentation: arm: Add bootargs to the table of added DT parameters Alexandre Ghiti
2023-06-26 14:36 ` [PATCH v4 2/3] Documentation: riscv: Add early boot document Alexandre Ghiti
2023-07-06 17:44 ` Palmer Dabbelt
2023-06-26 14:36 ` [PATCH v4 3/3] Documentation: riscv: Update boot image header since EFI stub is supported Alexandre Ghiti
2023-07-06 17:44 ` Palmer Dabbelt
2023-07-06 17:44 ` [PATCH v4 1/3] Documentation: arm: Add bootargs to the table of added DT parameters Palmer Dabbelt
2023-07-21 21:07 ` Jonathan Corbet
2023-07-22 10:49 ` Alexandre Ghiti
2023-07-22 19:00 ` Jonathan Corbet [this message]
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=871qgzbwkz.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=bjorn@rivosinc.com \
--cc=conor.dooley@microchip.com \
--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=songshuaishuai@tinylab.org \
--cc=sunilvl@ventanamicro.com \
/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