From: Peter Korsgaard <peter@korsgaard.com>
To: Titouan Christophe <titouan.christophe@mind.be>
Cc: buildroot@buildroot.org, git@jdknight.me,
thomas.petazzoni@bootlin.com, arnout@rnout.be,
thomas.perale@mind.be, ju.o@free.fr
Subject: Re: [Buildroot] [PATCH 2/3] linux: add first-class support for all upstream linux versions
Date: Sun, 11 Oct 2026 15:12:39 +0200 [thread overview]
Message-ID: <87se2ccreg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20261010201508.963412-3-titouan.christophe@mind.be> (Titouan Christophe's message of "Sat, 10 Oct 2026 22:15:07 +0200")
>>>>> "Titouan" == Titouan Christophe <titouan.christophe@mind.be> writes:
One more thing:
> Add new KConfig symbols for all actively supported longterm versions of the
> Linux kernel. This makes it easier for individual configs to follow updates
> of their kernels, without having to frequently update them. This should
> generally improve the security of the target systems, which receive frequent
> security updates while preserving a stable feature set.
> Signed-off-by: Titouan Christophe <titouan.christophe@mind.be>
> -ifeq ($(BR2_LINUX_KERNEL)$(BR2_LINUX_KERNEL_LATEST_VERSION),y)
> +ifeq ($(BR2_LINUX_KERNEL)$(BR2_LINUX_KERNEL_LATEST_SERIES),y)
> BR_NO_CHECK_HASH_FOR += $(LINUX_SOURCE)
> endif
When we do this then we also need to ensure the hashes for all these
versions are available, so I added the version symlinks like we have for
the linux-headers package:
lrwxrwxrwx 1 peko peko 11 Oct 11 15:08 5.10.271 -> before-6.17
lrwxrwxrwx 1 peko peko 11 Oct 11 15:08 5.15.222 -> before-6.17
lrwxrwxrwx 1 peko peko 11 Oct 11 15:07 6.1.189 -> before-6.17
lrwxrwxrwx 1 peko peko 11 Oct 11 15:07 6.12.112 -> before-6.17
lrwxrwxrwx 1 peko peko 9 Oct 11 15:07 6.18.55 -> from-6.17
lrwxrwxrwx 1 peko peko 11 Oct 11 15:07 6.6.158 -> before-6.17
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-11 13:12 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 [this message]
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
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=87se2ccreg.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=arnout@rnout.be \
--cc=buildroot@buildroot.org \
--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.