From: "Cédric Le Goater" <clg@kaod.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: Jean-Christophe Dubois <jcd@tribudubois.net>,
Igor Mitsyanko <i.mitsyanko@gmail.com>,
Andrey Smirnov <andrew.smirnov@gmail.com>,
Alexandre Iooss <erdnaxe@crans.org>,
Alistair Francis <alistair@alistair23.me>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [PATCH 1/7] docs/system/arm/stm32: List olimex-stm32-h405 in document title
Date: Mon, 21 Oct 2024 07:46:56 +0200 [thread overview]
Message-ID: <b396dc9f-c38a-48b4-9ee1-a3dd1eed2c15@kaod.org> (raw)
In-Reply-To: <20241018141332.942844-2-peter.maydell@linaro.org>
On 10/18/24 16:13, Peter Maydell wrote:
> List the olimex-stm32-h405 board in the document title, so that the
> board name appears in the table of contents in system/target-arm.rst.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> docs/system/arm/stm32.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/system/arm/stm32.rst b/docs/system/arm/stm32.rst
> index ca7a55841b4..511e3eb9ac1 100644
> --- a/docs/system/arm/stm32.rst
> +++ b/docs/system/arm/stm32.rst
> @@ -1,5 +1,5 @@
> -STMicroelectronics STM32 boards (``netduino2``, ``netduinoplus2``, ``stm32vldiscovery``)
> -========================================================================================
> +STMicroelectronics STM32 boards (``netduino2``, ``netduinoplus2``, ``olimex-stm32-h405``, ``stm32vldiscovery``)
> +===============================================================================================================
>
> The `STM32`_ chips are a family of 32-bit ARM-based microcontroller by
> STMicroelectronics.
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Thanks,
C.
next prev parent reply other threads:[~2024-10-21 5:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 14:13 [PATCH 0/7] docs/system/arm: Provide at least skeleton docs for all boards Peter Maydell
2024-10-18 14:13 ` [PATCH 1/7] docs/system/arm/stm32: List olimex-stm32-h405 in document title Peter Maydell
2024-10-21 5:46 ` Cédric Le Goater [this message]
2024-10-18 14:13 ` [PATCH 2/7] docs/system/arm: Don't use wildcard '*-bmc' in doc titles Peter Maydell
2024-10-21 5:56 ` Cédric Le Goater
2024-10-18 14:13 ` [PATCH 3/7] docs/system/arm: Split fby35 out from aspeed.rst Peter Maydell
2024-10-21 5:49 ` Cédric Le Goater
2024-10-18 14:13 ` [PATCH 4/7] docs/system/arm: Add placeholder doc for exynos4 boards Peter Maydell
2024-10-21 5:57 ` Cédric Le Goater
2024-10-18 14:13 ` [PATCH 5/7] docs/system/arm: Add placeholder doc for xlnx-zcu102 board Peter Maydell
2024-10-21 0:24 ` Alistair Francis
2024-10-18 14:13 ` [PATCH 6/7] docs/system/arm: Add placeholder docs for mcimx6ul-evk and mcimx7d-sabre Peter Maydell
2024-10-21 5:57 ` Cédric Le Goater
2024-10-18 14:13 ` [PATCH 7/7] docs/system/target-arm.rst: Remove "many boards are undocumented" note Peter Maydell
2024-10-21 0:25 ` Alistair Francis
2024-10-21 5:56 ` Cédric Le Goater
2024-10-20 20:34 ` [PATCH 0/7] docs/system/arm: Provide at least skeleton docs for all boards Alex Bennée
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=b396dc9f-c38a-48b4-9ee1-a3dd1eed2c15@kaod.org \
--to=clg@kaod.org \
--cc=alistair@alistair23.me \
--cc=andrew.smirnov@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=erdnaxe@crans.org \
--cc=i.mitsyanko@gmail.com \
--cc=jcd@tribudubois.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).