From: Tom Rini <trini@konsulko.com>
To: Richard Weinberger <richard@sigma-star.at>
Cc: Sam Protsenko <semen.protsenko@linaro.org>,
Richard Weinberger <richard@nod.at>,
upstream@sigma-star.at, u-boot@lists.denx.de,
ddrokosov@salutedevices.com, sjg@chromium.org,
tharvey@gateworks.com, ilias.apalodimas@linaro.org,
kojima.masahisa@socionext.com, upstream+uboot@sigma-star.at
Subject: Re: [RFC, PATCH] fdt: Make sure there is no stale initrd left
Date: Fri, 3 Oct 2025 15:01:49 -0600 [thread overview]
Message-ID: <20251003210149.GA6093@bill-the-cat> (raw)
In-Reply-To: <10664479.lqRGMn8q6B@nailgun>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
On Fri, Oct 03, 2025 at 09:09:20PM +0200, Richard Weinberger wrote:
> Sam,
>
> On Sonntag, 21. September 2025 01:01 Sam Protsenko wrote:
> > Hey Richard,
> >
> > Did you have a chance to look into reworking this patch? I'm still
> > carrying a revert locally (to make GBL EFI app work), and would like
> > to get rid of it. Please advice if you have a plan on handling this in
> > the near future.
>
> Before my vacation I had a look but found no nice solution.
> So, let's process with the revert.
>
> My current way to work around the problem is having these commands in
> my U-Boot scripts:
>
> fdt addr $fdt_addr
> fdt rm /chosen linux,initrd-start
> fdt rm /chosen linux,initrd-end
I do wonder if the best path forward is adding some opt-in CONFIG option
here?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-03 21:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 15:02 [RFC, PATCH] fdt: Make sure there is no stale initrd left Richard Weinberger
2025-06-12 22:15 ` Tom Rini
2025-07-08 22:58 ` Sam Protsenko
2025-07-09 6:24 ` Richard Weinberger
2025-07-09 17:05 ` Sam Protsenko
2025-07-10 14:40 ` Richard Weinberger
2025-07-10 17:20 ` Sam Protsenko
2025-09-20 23:01 ` Sam Protsenko
2025-10-03 19:09 ` Richard Weinberger
2025-10-03 21:01 ` Tom Rini [this message]
2025-10-04 8:05 ` Richard Weinberger
2025-10-17 22:08 ` Tom Rini
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=20251003210149.GA6093@bill-the-cat \
--to=trini@konsulko.com \
--cc=ddrokosov@salutedevices.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kojima.masahisa@socionext.com \
--cc=richard@nod.at \
--cc=richard@sigma-star.at \
--cc=semen.protsenko@linaro.org \
--cc=sjg@chromium.org \
--cc=tharvey@gateworks.com \
--cc=u-boot@lists.denx.de \
--cc=upstream+uboot@sigma-star.at \
--cc=upstream@sigma-star.at \
/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.