From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Marek Vasut <marex@denx.de>, Eddie James <eajames@linux.ibm.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Safae Ouajih <souajih@baylibre.com>
Subject: Re: [PATCH v2 5/5] boot: Don't allow kernel_noload with compression
Date: Tue, 14 Nov 2023 11:31:51 -0500 [thread overview]
Message-ID: <20231114163151.GW6601@bill-the-cat> (raw)
In-Reply-To: <20231112035001.103897-2-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
On Sat, Nov 11, 2023 at 08:49:57PM -0700, Simon Glass wrote:
> It is not possible to execute the kernel in-place without loading it.
> Detect this and show an error, to avoid a crash.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-11-14 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 3:49 [PATCH v2 0/5] bootm: Handle compressed arm64 images with bootm Simon Glass
2023-11-12 3:49 ` [PATCH v2 1/5] image: Correct load_bug typo Simon Glass
2023-11-14 16:40 ` Tom Rini
2023-11-12 3:49 ` [PATCH v2 2/5] image: Show the load address when decompressing Simon Glass
2023-11-14 22:36 ` Tom Rini
2023-11-12 3:49 ` [PATCH v2 3/5] bootm: Allow omitting the load address Simon Glass
2023-11-14 16:38 ` Tom Rini
2023-11-14 18:04 ` Tom Rini
2023-11-18 17:10 ` Simon Glass
2023-11-12 3:49 ` [PATCH v2 4/5] bootm: Move arm64-image processing later Simon Glass
2023-11-12 3:49 ` [PATCH v2 5/5] boot: Don't allow kernel_noload with compression Simon Glass
2023-11-14 16:31 ` Tom Rini [this message]
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=20231114163151.GW6601@bill-the-cat \
--to=trini@konsulko.com \
--cc=eajames@linux.ibm.com \
--cc=ilias.apalodimas@linaro.org \
--cc=marex@denx.de \
--cc=mkorpershoek@baylibre.com \
--cc=sjg@chromium.org \
--cc=souajih@baylibre.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