U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Mattijs Korpershoek <mkorpershoek@baylibre.com>,
	Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>,
	Alexander Dahl <ada@thorsis.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Bin Meng <bmeng.cn@gmail.com>,
	Caleb Connolly <caleb.connolly@linaro.org>,
	E Shattow <lucent@gmail.com>, Jaewon Jung <jaewon8868@gmail.com>,
	Janne Grunau <j@jannau.net>,
	Joao Marcos Costa <jmcosta944@gmail.com>,
	Marek Vasut <marex@denx.de>, Michal Simek <michal.simek@amd.com>,
	Nam Cao <namcao@linutronix.de>,
	Quentin Schulz <quentin.schulz@cherry.de>,
	Sam Protsenko <semen.protsenko@linaro.org>,
	Sumit Garg <sumit.garg@linaro.org>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 02/13] doc: Move bootstd into its own directory
Date: Tue, 16 Jul 2024 10:18:01 -0600	[thread overview]
Message-ID: <20240716161801.GE561963@bill-the-cat> (raw)
In-Reply-To: <CAFLszTim9eiN5rObbZbGYa6ZgCV0G=7s6v1Bji3QO=o1fOiiaQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5119 bytes --]

On Tue, Jul 16, 2024 at 08:04:38AM +0100, Simon Glass wrote:
> Hi Heinrich,
> 
> On Mon, 15 Jul 2024 at 22:58, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> >
> > On 7/15/24 12:13, Simon Glass wrote:
> > > Before adding more files, move the bootstd docs into a new directory,
> > > with an index.
> > >
> > > Signed-off-by: Simon Glass <sjg@chromium.org>
> > > ---
> > >
> > >   MAINTAINERS                                       |  2 +-
> > >   doc/board/starfive/milk-v_mars_cm.rst             |  2 +-
> > >   doc/develop/board_best_practices.rst              |  2 +-
> > >   doc/develop/bootstd/index.rst                     |  9 +++++++++
> > >   doc/develop/{bootstd.rst => bootstd/overview.rst} | 14 +++++++-------
> > >   doc/develop/index.rst                             |  2 +-
> > >   doc/usage/cmd/bootdev.rst                         |  2 +-
> > >   doc/usage/cmd/bootflow.rst                        |  2 +-
> > >   doc/usage/cmd/bootmeth.rst                        |  2 +-
> > >   doc/usage/environment.rst                         |  2 +-
> > >   10 files changed, 24 insertions(+), 15 deletions(-)
> > >   create mode 100644 doc/develop/bootstd/index.rst
> > >   rename doc/develop/{bootstd.rst => bootstd/overview.rst} (99%)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 9bee9284cca..86b830aa997 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -927,7 +927,7 @@ F:        boot/bootmeth*.c
> > >   F:  boot/bootstd.c
> > >   F:  cmd/bootdev.c
> > >   F:  cmd/bootflow.c
> > > -F:   doc/develop/bootstd.rst
> > > +F:   doc/develop/bootstd/
> > >   F:  doc/usage/bootdev.rst
> > >   F:  doc/usage/bootflow.rst
> > >   F:  doc/usage/bootmeth.rst
> > > diff --git a/doc/board/starfive/milk-v_mars_cm.rst b/doc/board/starfive/milk-v_mars_cm.rst
> > > index b31de6043bb..52d4e5e9098 100644
> > > --- a/doc/board/starfive/milk-v_mars_cm.rst
> > > +++ b/doc/board/starfive/milk-v_mars_cm.rst
> > > @@ -89,7 +89,7 @@ provide a default value.
> > >
> > >   The variable *$fdtfile* is used in the boot process to automatically load
> > >   a device-tree provided by the operating system. For details of the boot
> > > -process refer to the :doc:`U-Boot Standard Boot <../../../develop/bootstd>`
> > > +process refer to the :doc:`/develop/bootstd/index`
> > >   description.
> > >
> > >   Boot source selection
> > > diff --git a/doc/develop/board_best_practices.rst b/doc/develop/board_best_practices.rst
> > > index f44401eab7d..09632c80ce7 100644
> > > --- a/doc/develop/board_best_practices.rst
> > > +++ b/doc/develop/board_best_practices.rst
> > > @@ -7,7 +7,7 @@ In addition to the regular best practices such as using :doc:`checkpatch` and
> > >   following the :doc:`docstyle` and the :doc:`codingstyle` there are some things
> > >   which are specific to creating a new board port.
> > >
> > > -* Implement :doc:`bootstd` to ensure that most operating systems will be
> > > +* Implement :doc:`bootstd/index` to ensure that most operating systems will be
> > >     supported by the platform.
> > >
> > >   * The platform defconfig file must be generated via `make savedefconfig`.
> > > diff --git a/doc/develop/bootstd/index.rst b/doc/develop/bootstd/index.rst
> > > new file mode 100644
> > > index 00000000000..f4f87c7787c
> > > --- /dev/null
> > > +++ b/doc/develop/bootstd/index.rst
> > > @@ -0,0 +1,9 @@
> > > +.. SPDX-License-Identifier: GPL-2.0+:
> > > +
> > > +Standard Boot
> > > +=============
> > > +
> > > +.. toctree::
> > > +   :maxdepth: 2
> > > +
> > > +   overview
> > > diff --git a/doc/develop/bootstd.rst b/doc/develop/bootstd/overview.rst
> > > similarity index 99%
> > > rename from doc/develop/bootstd.rst
> > > rename to doc/develop/bootstd/overview.rst
> > > index 34631089ae0..761f61a573b 100644
> > > --- a/doc/develop/bootstd.rst
> > > +++ b/doc/develop/bootstd/overview.rst
> > > @@ -1,7 +1,7 @@
> > >   .. SPDX-License-Identifier: GPL-2.0+:
> > >
> > > -U-Boot Standard Boot
> > > -====================
> > > +Standard Boot Overview
> > > +======================
> > >
> >
> >
> >
> > The text is not optimized for readability, e.g.
> >
> > "- bootdev  - a device which can hold or access a distro (e.g. MMC,
> > Ethernet)"
> >
> > Please, consistently replace the non-words in the boot standard
> > documentation:
> >
> > %s/bootdev/boot device/
> > %s/bootmeth/boot method/
> > %s/bootflow/boot flow/
> 
> I do want to keep the terms, It is easy to search for bootdev or
> bootmeth in the code and docs. Once people learn what they mean it is
> pretty simple.

I agree, this is the documentation for "bootdev" and "bootmeth" and
"bootflow" not for "boot device" and so forth.

> > "distro" isn't a dictionary word either. Do you mean operating system?
> 
> I mean a linux distro, in the sense that 'distro boot' uses it.

Maybe an initial statement early about starting your operating system
distribution (distro), and then it's OK to say distro later on? This
does also work on non-Linux distributions :)

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2024-07-16 16:18 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 10:13 [PATCH 00/13] doc: Add documentation for bootmeths Simon Glass
2024-07-15 10:13 ` [PATCH 01/13] MAINTAINERS: Rename BOOTDEVICE Simon Glass
2024-07-15 13:34   ` Quentin Schulz
2024-07-16  7:04   ` Mattijs Korpershoek
2024-07-15 10:13 ` [PATCH 02/13] doc: Move bootstd into its own directory Simon Glass
2024-07-15 14:12   ` Quentin Schulz
2024-07-15 21:58   ` Heinrich Schuchardt
2024-07-16  7:04     ` Simon Glass
2024-07-16 16:18       ` Tom Rini [this message]
2024-07-19 15:05         ` Simon Glass
2024-07-16  7:09   ` Mattijs Korpershoek
2024-07-15 10:13 ` [PATCH 03/13] doc: Add a description for bootmeth_extlinux Simon Glass
2024-07-15 14:12   ` Quentin Schulz
2024-07-15 22:30   ` Heinrich Schuchardt
2024-07-16  7:04     ` Simon Glass
2024-07-16  7:17   ` Mattijs Korpershoek
2024-07-15 10:13 ` [PATCH 04/13] doc: Add a description for bootmeth_pxe Simon Glass
2024-07-15 14:13   ` Quentin Schulz
2024-07-15 22:42   ` Heinrich Schuchardt
2024-07-16  7:04     ` Simon Glass
2024-07-16  7:21   ` Mattijs Korpershoek
2024-07-15 10:13 ` [PATCH 05/13] doc: Add a description for bootmeth_qfw Simon Glass
2024-07-15 14:13   ` Quentin Schulz
2024-07-15 22:56   ` Heinrich Schuchardt
2024-07-16  7:04     ` Simon Glass
2024-07-16  7:25   ` Mattijs Korpershoek
2024-07-15 10:13 ` [PATCH 06/13] doc: Add a description for bootmeth_cros Simon Glass
2024-07-15 14:13   ` Quentin Schulz
2024-07-15 23:02   ` Heinrich Schuchardt
2024-07-16  7:04     ` Simon Glass
2024-07-16  7:28   ` Mattijs Korpershoek
2024-07-15 10:13 ` [PATCH 07/13] doc: Add a description for bootmeth_sandbox Simon Glass
2024-07-15 14:13   ` Quentin Schulz
2024-07-16  7:30   ` Mattijs Korpershoek
2024-07-15 10:13 ` [PATCH 08/13] bootstd: Tidy up comments on the boothmeth drivers Simon Glass
2024-07-15 14:14   ` Quentin Schulz
2024-07-15 23:11   ` Heinrich Schuchardt
2024-07-15 10:13 ` [PATCH 09/13] bootstd: Correct handling of script from network Simon Glass
2024-07-15 10:13 ` [PATCH 10/13] doc: Add a description for bootmeth_script Simon Glass
2024-07-15 14:14   ` Quentin Schulz
2024-07-15 10:13 ` [PATCH 11/13] doc: Add a link to VBE from the bootstd docs Simon Glass
2024-07-15 14:14   ` Quentin Schulz
2024-07-15 23:09   ` Heinrich Schuchardt
2024-07-15 10:13 ` [PATCH 12/13] boot: Correct indentation in efi bootmeth Simon Glass
2024-07-15 14:14   ` Quentin Schulz
2024-07-15 23:05   ` Heinrich Schuchardt
2024-07-22  6:52   ` Ilias Apalodimas
2024-07-15 10:13 ` [PATCH 13/13] doc: Describe the bootstd settings Simon Glass
2024-07-15 14:15   ` Quentin Schulz

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=20240716161801.GE561963@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=abdellatif.elkhlifi@arm.com \
    --cc=ada@thorsis.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bmeng.cn@gmail.com \
    --cc=caleb.connolly@linaro.org \
    --cc=j@jannau.net \
    --cc=jaewon8868@gmail.com \
    --cc=jmcosta944@gmail.com \
    --cc=lucent@gmail.com \
    --cc=marex@denx.de \
    --cc=michal.simek@amd.com \
    --cc=mkorpershoek@baylibre.com \
    --cc=namcao@linutronix.de \
    --cc=quentin.schulz@cherry.de \
    --cc=semen.protsenko@linaro.org \
    --cc=sjg@chromium.org \
    --cc=sumit.garg@linaro.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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