From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Jagan Teki <jagan@amarulasolutions.com>,
Andre Przywara <andre.przywara@arm.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>
Subject: Re: [PATCH v5 3/8] efi_loader: bootstd: Drop bootmgr for sunxi
Date: Wed, 13 Nov 2024 11:50:17 -0600 [thread overview]
Message-ID: <20241113175017.GS3600562@bill-the-cat> (raw)
In-Reply-To: <20241113150938.1534931-4-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
On Wed, Nov 13, 2024 at 08:09:33AM -0700, Simon Glass wrote:
> This causes problems with the boot order, so drop it until we can figure
> out a better way to know when bootmgr should be used.
>
> Link: https://lore.kernel.org/u-boot/20241112171205.4e80548d@donnerap.manchester.arm.com/
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
I would really prefer a short summary of the contents of the link in the
commit message. I'm not NAK'ing the patch as-is, but it would be helpful
when revisiting this if there was a short explanation of the problem to
solve here and not just "problems with the boot order". Thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-11-13 17:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 15:09 [PATCH v5 0/8] bootstd: sunxi: Migrate to standard boot Simon Glass
2024-11-13 15:09 ` [PATCH v5 1/8] bootstd: Avoid depending on BLK Simon Glass
2024-11-13 17:47 ` Tom Rini
2024-11-14 3:53 ` Simon Glass
2024-11-14 14:22 ` Tom Rini
2024-11-15 14:27 ` Simon Glass
2024-11-15 14:37 ` Tom Rini
2024-11-13 15:09 ` [PATCH v5 2/8] sunxi: Add a bootmeth for FEL Simon Glass
2024-11-13 15:09 ` [PATCH v5 3/8] efi_loader: bootstd: Drop bootmgr for sunxi Simon Glass
2024-11-13 17:50 ` Tom Rini [this message]
2024-11-15 14:21 ` Simon Glass
2024-11-23 2:08 ` Andre Przywara
2024-11-23 4:06 ` Heinrich Schuchardt
2024-11-23 13:07 ` Andre Przywara
2024-11-23 16:56 ` Ilias Apalodimas
2024-11-16 7:37 ` Heinrich Schuchardt
2024-11-13 15:09 ` [PATCH v5 4/8] RFC: Revert "bootstd: Make efi_mgr bootmeth work for non-sandbox setups" Simon Glass
2024-11-13 17:52 ` Tom Rini
2025-01-05 2:50 ` Heinrich Schuchardt
2025-01-09 15:01 ` Simon Glass
2025-01-09 15:04 ` Tom Rini
2025-01-09 15:11 ` Simon Glass
2025-01-09 15:22 ` Tom Rini
2025-01-10 13:41 ` Simon Glass
2025-01-10 17:05 ` Tom Rini
2025-01-15 13:22 ` Simon Glass
2025-01-15 14:33 ` Tom Rini
2024-11-13 15:09 ` [PATCH v5 5/8] sunxi: Move to bootstd Simon Glass
2024-11-13 15:09 ` [PATCH v5 6/8] sunxi: Drop old distro boot variables Simon Glass
2024-11-13 15:09 ` [PATCH v5 7/8] env: Provide a work-around for unquoting fdtfile Simon Glass
2024-11-13 17:53 ` Tom Rini
2025-03-10 22:26 ` Tom Rini
2024-11-13 15:09 ` [PATCH v5 8/8] sunxi: Move to text environment Simon Glass
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=20241113175017.GS3600562@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jagan@amarulasolutions.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mkorpershoek@baylibre.com \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.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