Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Quentin Schulz <foss+buildroot@0leil.net>
Cc: buildroot@buildroot.org,
	Quentin Schulz <quentin.schulz@cherry.de>,
	Ozan Durgut <ozandurgut.2001@hotmail.com>
Subject: Re: [Buildroot] [PATCH] boot/uboot: fix externally provided env file not used on 2025.10
Date: Fri, 2 Jan 2026 23:39:50 +0100	[thread overview]
Message-ID: <20260102233950.22f75fcc@windsurf> (raw)
In-Reply-To: <20251124-uboot-env-rename-v1-1-7ac5a21da6e2@cherry.de>

On Mon, 24 Nov 2025 13:26:54 +0100
Quentin Schulz <foss+buildroot@0leil.net> wrote:

> From: Quentin Schulz <quentin.schulz@cherry.de>
> 
> fb5235239aad ("env: Rename DEFAULT_ENV_FILE to
> ENV_DEFAULT_ENV_TEXT_FILE") renamed the Kconfig symbols and thus we need
> to adapt the U-Boot package in Buildroot to support it.
> 
> Fixes: 128c26f2875d ("boot/uboot: bump to version 2025.10")
> Reported-by: Ozan Durgut <ozandurgut.2001@hotmail.com>
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
> Only roughly build tested, warp7_defconfig modified:
> - to use Kconfig for U-Boot,
> - to add a dummy environment text file,

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-01-02 22:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 12:26 [Buildroot] [PATCH] boot/uboot: fix externally provided env file not used on 2025.10 Quentin Schulz
2026-01-02 22:39 ` Thomas Petazzoni via buildroot [this message]
2026-01-13 19:48 ` Arnout Vandecappelle via buildroot

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=20260102233950.22f75fcc@windsurf \
    --to=buildroot@buildroot.org \
    --cc=foss+buildroot@0leil.net \
    --cc=ozandurgut.2001@hotmail.com \
    --cc=quentin.schulz@cherry.de \
    --cc=thomas.petazzoni@bootlin.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