From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Titouan Christophe via buildroot <buildroot@buildroot.org>
Cc: Titouan Christophe <titouan.christophe@mind.be>,
ju.o@free.fr, thomas.petazzoni@bootlin.com, arnout@rnout.be,
git@jdknight.me, thomas.perale@mind.be
Subject: Re: [Buildroot] [PATCH 3/3] configs: update defconfigs with custom versions to BR2_LINUX_KERNEL_LATEST_X_Y
Date: Sun, 11 Oct 2026 19:45:17 +0300 [thread overview]
Message-ID: <877bjo425e.fsf@tarshish> (raw)
In-Reply-To: <20261010201508.963412-4-titouan.christophe@mind.be> (Titouan Christophe via buildroot's message of "Sat, 10 Oct 2026 22:15:08 +0200")
Hi Titouan,
On Sat, Oct 10 2026, Titouan Christophe via buildroot wrote:
> Update all defconfigs that are using a custom Linux version based on a
> longterm supported Linux version so they use the newly introduced symbols.
This is a significant policy change for Buildroot. The configs/
directory is meant to carry configurations that are "known to work",
according to adding-board-support section in Buildroot manual
(docs/manual/adding-board-support.adoc).
Automatic update of the kernel component without actual hardware test
risks introducing regressions that make the system unbootable.
For this reason adding-board-support section also says:
> Always use fixed versions or commit hashes for the different
> components, not the "latest" version.
If we intend to change this policy I think we should discuss the
motivation on the list. In case such discussion did take place, this
comment should reference that discussion. In any case, the manual should
also update to reflect the current policy.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-11 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 20:15 [Buildroot] [PATCH 0/3] Add first-class support for all active upstream Linux versions Titouan Christophe via buildroot
2026-10-10 20:15 ` [Buildroot] [PATCH 1/3] linux: always select host-uboot-tools for mips Titouan Christophe via buildroot
2026-10-11 12:30 ` Peter Korsgaard
2026-10-10 20:15 ` [Buildroot] [PATCH 2/3] linux: add first-class support for all upstream linux versions Titouan Christophe via buildroot
2026-10-11 12:32 ` Peter Korsgaard
2026-10-11 13:12 ` Peter Korsgaard
2026-10-10 20:15 ` [Buildroot] [PATCH 3/3] configs: update defconfigs with custom versions to BR2_LINUX_KERNEL_LATEST_X_Y Titouan Christophe via buildroot
2026-10-11 13:05 ` Peter Korsgaard
2026-10-11 13:08 ` Titouan Christophe via buildroot
2026-10-11 16:45 ` Baruch Siach via buildroot [this message]
2026-10-11 19:10 ` Titouan Christophe via buildroot
2026-10-12 6:04 ` Baruch Siach via buildroot
2026-10-12 8:35 ` Titouan Christophe via buildroot
2026-10-12 10:40 ` Arnout Vandecappelle via buildroot
2026-10-13 5:58 ` Baruch Siach via buildroot
2026-10-13 5:55 ` Baruch Siach via buildroot
2026-10-11 19:29 ` Arnout Vandecappelle via buildroot
2026-10-11 19:37 ` Titouan Christophe 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=877bjo425e.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=arnout@rnout.be \
--cc=baruch@tkos.co.il \
--cc=git@jdknight.me \
--cc=ju.o@free.fr \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.com \
--cc=titouan.christophe@mind.be \
/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.