All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Alexandre IOOSS <erdnaxe@crans.org>
Cc: "open list:STM32F100" <qemu-arm@nongnu.org>,
	"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: [PATCH 2/2] stm32vldiscovery: Add the STM32VLDISCOVERY Machine
Date: Tue, 15 Jun 2021 10:07:24 +0100	[thread overview]
Message-ID: <CAFEAcA8rz3XkBzieMGZf7TbMkv-RPdgQG-LD06-f6kTLo-G2WQ@mail.gmail.com> (raw)
In-Reply-To: <4fdbc225-3c4a-ba38-2fa6-5a031e6a1845@crans.org>

On Tue, 15 Jun 2021 at 08:16, Alexandre IOOSS <erdnaxe@crans.org> wrote:
>
> On 6/14/21 5:52 PM, Peter Maydell wrote:
> > Could you add some documentation for the new board, please?
> > This lives in docs/system/arm. Commit c9f8511ea8d2b807 gives
> > an example of adding docs for a board.

> Should I rather:
> 1. Add `docs/system/arm/stm32vldiscovery.rst` to document only this new
> machine?
> 2. Add `docs/system/arm/stm32discovery.rst` to document this new machine
> and future STM32 Discovery boards?
> 3. Add `docs/system/arm/stm32.rst` to document all STM32-based boards?
>
> STM32 boards share a lot in common so I believe option 3 is more
> appropriate, what is your opinion?
> If we go with option 3, I can also try to document the Netduino Plus 2
> (maybe in another commit, or another patchset later).

Yes, I think that a shared stm32.rst is probably the best thing.
If you want to document the netduino boards too that would be
great, but I don't insist on it.

thanks
-- PMM


  parent reply	other threads:[~2021-06-15  9:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 16:10 [PATCH 0/2] STM32VLDISCOVERY Machine Model Alexandre Iooss
2021-06-08 16:10 ` [PATCH 1/2] stm32f100: Add the stm32f100 SoC Alexandre Iooss
2021-06-14 16:04   ` Peter Maydell
2021-06-15  7:56     ` Alexandre IOOSS
2021-06-15  7:41   ` Alistair Francis
2021-06-15  7:49     ` Alexandre IOOSS
2021-06-15  8:04       ` Alistair Francis
2021-06-15  9:15         ` Alexandre IOOSS
2021-06-15 10:40           ` Alistair Francis
2021-06-08 16:10 ` [PATCH 2/2] stm32vldiscovery: Add the STM32VLDISCOVERY Machine Alexandre Iooss
2021-06-14 15:52   ` Peter Maydell
2021-06-15  7:16     ` Alexandre IOOSS
2021-06-15  7:50       ` Alistair Francis
2021-06-15  9:07       ` Peter Maydell [this message]
2021-06-14 16:05 ` [PATCH 0/2] STM32VLDISCOVERY Machine Model Peter Maydell
2021-06-14 16:16   ` Philippe Mathieu-Daudé

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=CAFEAcA8rz3XkBzieMGZf7TbMkv-RPdgQG-LD06-f6kTLo-G2WQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=erdnaxe@crans.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.