From: Peter Korsgaard <peter@korsgaard.com>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Bernd Kuhls <bernd@kuhls.net>,
Angelo Compagnucci <angelo@amarulasolutions.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/3] linux: bump 5.10 CIP kernel versions
Date: Wed, 17 Jan 2024 13:50:33 +0100 [thread overview]
Message-ID: <87ttnci0o6.fsf@48ers.dk> (raw)
In-Reply-To: <20240115214137.2350453-4-petr.vorel@gmail.com> (Petr Vorel's message of "Mon, 15 Jan 2024 22:41:37 +0100")
>>>>> "Petr" == Petr Vorel <petr.vorel@gmail.com> writes:
> Bump CIP to 5.10.205-cip42, CIP RT to 5.10.201-cip41-rt17.
> Use sha256sums.asc from kernel.org.
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> linux/Config.in | 4 ++--
> linux/linux.hash | 6 +++---
> 2 files changed, 5 insertions(+), 5 deletions(-)
> diff --git a/linux/Config.in b/linux/Config.in
> index 4528d8eacc..36649d3391 100644
> --- a/linux/Config.in
> +++ b/linux/Config.in
> @@ -32,7 +32,7 @@ config BR2_LINUX_KERNEL_LATEST_VERSION
> select BR2_TOOLCHAIN_HEADERS_AT_LEAST_6_7 if BR2_KERNEL_HEADERS_AS_KERNEL
> config BR2_LINUX_KERNEL_LATEST_CIP_VERSION
> - bool "Latest CIP SLTS version (5.10.162-cip24)"
> + bool "Latest CIP SLTS version (5.10.205-cip42)"
> select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_10 if BR2_KERNEL_HEADERS_AS_KERNEL
> help
> CIP launched in the spring of 2016 to address the needs of
> @@ -52,7 +52,7 @@ config BR2_LINUX_KERNEL_LATEST_CIP_VERSION
> https://www.cip-project.org
> config BR2_LINUX_KERNEL_LATEST_CIP_RT_VERSION
> - bool "Latest CIP RT SLTS version (5.10.162-cip24-rt10)"
> + bool "Latest CIP RT SLTS version (5.10.201-cip41-rt17)"
> select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_10 if BR2_KERNEL_HEADERS_AS_KERNEL
> help
> Same as the CIP version, but this is the PREEMPT_RT realtime
> diff --git a/linux/linux.hash b/linux/linux.hash
> index efd0dac4cf..6e75e017d3 100644
> --- a/linux/linux.hash
> +++ b/linux/linux.hash
> @@ -7,9 +7,9 @@ sha256 9025147a09547f28ec8f496c12efc30bd2fc03b2824a668e8636b2ca0ef1fb6e linux-
> sha256 42d28def2cc1502251edbfeaca3b25ee764ad1e471b6c703ccb2267f38471c43 linux-5.4.267.tar.xz
> # From https://www.kernel.org/pub/linux/kernel/v4.x/sha256sums.asc
> sha256 da82425c7410623dfb2405915347ee9617fc0e33a63ca821c33aeed160cddae8 linux-4.19.305.tar.xz
> -# Locally computed
> -sha256 fb0edc3c18e47d2b6974cb0880a0afb5c3fa08f50ee87dfdf24349405ea5f8ae linux-cip-5.10.162-cip24.tar.gz
> -sha256 b5539243f187e3d478d76d44ae13aab83952c94b885ad889df6fa9997e16a441 linux-cip-5.10.162-cip24-rt10.tar.gz
> +# From https://www.kernel.org/pub/linux/kernel/projects/cip/5.10/sha256sums.asc
> +sha256 b4734a7a22a30f3c20f9437c366bde0dd584bebe836d1ef622d4c1d7205e6f54 linux-cip-5.10.205-cip42.tar.xz
> +sha256 b1dc1779a9b8e05c1b547c2b3f2b19c5829504431f09c1a82e24b98d1395c4a8 linux-cip-5.10.201-cip41-rt17.tar.xz
This cannot work without updating the strings in
BR2_LINUX_KERNEL_VERSION?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-01-17 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 21:41 [Buildroot] [PATCH 0/3] Bump kernel versions Petr Vorel
2024-01-15 21:41 ` [Buildroot] [PATCH 1/3] linux: bump latest version to 6.6 Petr Vorel
2024-01-17 12:51 ` Peter Korsgaard
2024-01-15 21:41 ` [Buildroot] [PATCH 2/3] {linux, linux-headers}: bump 5.{10, 15}.x / 6.{1, 6}.x series Petr Vorel
2024-02-05 14:34 ` Thomas Petazzoni via buildroot
2024-01-15 21:41 ` [Buildroot] [PATCH 3/3] linux: bump 5.10 CIP kernel versions Petr Vorel
2024-01-17 12:50 ` Peter Korsgaard [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=87ttnci0o6.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=angelo@amarulasolutions.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=petr.vorel@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=yann.morin.1998@free.fr \
/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.