mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: Re: [PATCH 0/5] blspec: sort entries according to specification
Date: Mon, 23 Feb 2026 12:11:05 +0100	[thread overview]
Message-ID: <177184506583.220970.9818438793267958904.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260209090911.3561875-1-a.fatoum@barebox.org>


On Mon, 09 Feb 2026 10:08:50 +0100, Ahmad Fatoum wrote:
> Boot entries generated from bootloader spec are currently sorted by the
> order the files are read from the file system.
> 
> This is inadequate if we have multiple entries with different kernels
> and we want to sort the newer kernels higher.
> 
> The UAPI.1 Boot Loader Specification defines an algorithm[1] to order the
> entries that takes care of this, so implement it into barebox.
> 
> [...]

Applied, thanks!

[1/5] boot: aggregate bootentry provider entries one by one
      https://git.pengutronix.de/cgit/barebox/commit/?id=6f0f9a44ea2b (link may not be stable)
[2/5] blspec: sort entries according to specification
      https://git.pengutronix.de/cgit/barebox/commit/?id=6bf9cd6f5347 (link may not be stable)
[3/5] boot: give struct bootentry a path member
      https://git.pengutronix.de/cgit/barebox/commit/?id=2c4d3f594dc4 (link may not be stable)
[4/5] commands: boot: support file path in boot -M for default entry
      https://git.pengutronix.de/cgit/barebox/commit/?id=c5ce2a86e1ad (link may not be stable)
[5/5] test: self: add bootloader spec files test
      https://git.pengutronix.de/cgit/barebox/commit/?id=989dac4d649e (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2026-02-23 11:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09  9:08 Ahmad Fatoum
2026-02-09  9:08 ` [PATCH 1/5] boot: aggregate bootentry provider entries one by one Ahmad Fatoum
2026-02-09  9:08 ` [PATCH 2/5] blspec: sort entries according to specification Ahmad Fatoum
2026-02-23 11:06   ` Sascha Hauer
2026-02-23 11:08     ` Ahmad Fatoum
2026-02-09  9:08 ` [PATCH 3/5] boot: give struct bootentry a path member Ahmad Fatoum
2026-02-09  9:08 ` [PATCH 4/5] commands: boot: support file path in boot -M for default entry Ahmad Fatoum
2026-02-09  9:08 ` [PATCH 5/5] test: self: add bootloader spec files test Ahmad Fatoum
2026-02-23 11:11 ` 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=177184506583.220970.9818438793267958904.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.org \
    /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