From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Simon Glass <sjg@chromium.org>,
U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Simon Glass <sjg@chromium.org>,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [PATCH v2 01/14] MAINTAINERS: Rename BOOTDEVICE
Date: Tue, 16 Jul 2024 09:34:41 +0200 [thread overview]
Message-ID: <875xt5okmm.fsf@baylibre.com> (raw)
In-Reply-To: <20240716070419.1897560-2-sjg@chromium.org>
Hi Simon,
Thank you for the patch.
On mar., juil. 16, 2024 at 08:04, Simon Glass <sjg@chromium.org> wrote:
> Rename this to BOOTSTD which is the normal name for the feature.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
> ---
>
> (no changes since v1)
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 2c6de3a1d84..9bee9284cca 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -918,7 +918,7 @@ F: drivers/block/blkmap.c
> F: include/blkmap.h
> F: test/dm/blkmap.c
>
> -BOOTDEVICE
> +BOOTSTD
> M: Simon Glass <sjg@chromium.org>
> S: Maintained
> F: boot/bootdev*.c
> --
> 2.34.1
next prev parent reply other threads:[~2024-07-16 7:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 7:04 [PATCH v2 00/14] doc: Add documentation for bootmeths Simon Glass
2024-07-16 7:04 ` [PATCH v2 01/14] MAINTAINERS: Rename BOOTDEVICE Simon Glass
2024-07-16 7:34 ` Mattijs Korpershoek [this message]
2024-07-16 7:04 ` [PATCH v2 02/14] doc: Move bootstd into its own directory Simon Glass
2024-07-16 7:35 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 03/14] doc: Mention automatic binding of bootmeths Simon Glass
2024-07-16 7:36 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 04/14] doc: Add a description for bootmeth_extlinux Simon Glass
2024-07-16 7:37 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 05/14] doc: Add a description for bootmeth_pxe Simon Glass
2024-07-16 7:38 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 06/14] doc: Add a description for bootmeth_qfw Simon Glass
2024-07-16 7:40 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 07/14] doc: Add a description for bootmeth_cros Simon Glass
2024-07-16 7:41 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 08/14] doc: Add a description for bootmeth_sandbox Simon Glass
2024-07-16 7:41 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 09/14] bootstd: Tidy up comments on the boothmeth drivers Simon Glass
2024-07-16 7:42 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 10/14] bootstd: Correct handling of script from network Simon Glass
2024-07-16 7:45 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 11/14] doc: Add a description for bootmeth_script Simon Glass
2024-07-16 7:49 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 12/14] doc: Add a link to VBE from the bootstd docs Simon Glass
2024-07-16 7:50 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 13/14] boot: Correct indentation in efi bootmeth Simon Glass
2024-07-16 7:50 ` Mattijs Korpershoek
2024-07-16 7:04 ` [PATCH v2 14/14] doc: Describe the bootstd settings Simon Glass
2024-07-16 7:51 ` Mattijs Korpershoek
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=875xt5okmm.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--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