From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "Claude Sonnet 4.5" <noreply@anthropic.com>
Subject: Re: [PATCH 1/4] of: fdt: implement of_del_reserve_entry
Date: Fri, 23 Jan 2026 08:45:16 +0100 [thread overview]
Message-ID: <176915431650.3866187.4327761330604404177.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260121113738.1485637-1-a.fatoum@pengutronix.de>
On Wed, 21 Jan 2026 12:36:46 +0100, Ahmad Fatoum wrote:
> OF_MAX_RESERVE_MAP is only 16 and we have instances in the code that add
> reserve entries in device tree fixups, which means it can be exhausted
> when fixups are applied repeatedly.
>
> Whether it's still apt in 2026 to use reserve entries is a different
> discussion, but let's just add a way to delete reserved entries again in
> cleanup code.
>
> [...]
Applied, thanks!
[1/4] of: fdt: implement of_del_reserve_entry
https://git.pengutronix.de/cgit/barebox/commit/?id=5e28508ce3a9 (link may not be stable)
[2/4] ARM: sm: fix repeated call to of_add_reserve_entry on every fixup
https://git.pengutronix.de/cgit/barebox/commit/?id=946388dee629 (link may not be stable)
[3/4] bootm: delete initrd reserve entry on bootm_boot return
https://git.pengutronix.de/cgit/barebox/commit/?id=8eea7a84b975 (link may not be stable)
[4/4] video: stmfb: add screen base only once
https://git.pengutronix.de/cgit/barebox/commit/?id=31e8d676439c (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-01-23 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 11:36 Ahmad Fatoum
2026-01-21 11:36 ` [PATCH 2/4] ARM: sm: fix repeated call to of_add_reserve_entry on every fixup Ahmad Fatoum
2026-01-21 11:36 ` [PATCH 3/4] bootm: delete initrd reserve entry on bootm_boot return Ahmad Fatoum
2026-01-21 11:36 ` [PATCH 4/4] video: stmfb: add screen base only once Ahmad Fatoum
2026-01-23 7:45 ` Sascha Hauer [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=176915431650.3866187.4327761330604404177.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=noreply@anthropic.com \
/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