From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] package/linux-headers: drop 5.16.x option
Date: Fri, 13 May 2022 18:36:39 +0200 [thread overview]
Message-ID: <20220513163639.GR1597494@scaer> (raw)
In-Reply-To: <20220513144215.2598981-3-peter@korsgaard.com>
Peter, All,
On 2022-05-13 16:42 +0200, Peter Korsgaard spake thusly:
> The 5.16.x series is now EOL upstream, so drop the linux-headers option and
> add legacy handling for it.
See my review of the next patch.
Both this one and the next I marked as changes-requested in patchwork.
Regards,
Yann E. MORIN.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> Config.in.legacy | 7 +++++++
> linux/linux.hash | 1 -
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/Config.in.legacy b/Config.in.legacy
> index 806e995bd1..95b9d784d3 100644
> --- a/Config.in.legacy
> +++ b/Config.in.legacy
> @@ -146,6 +146,13 @@ endif
>
> comment "Legacy options removed in 2022.05"
>
> +config BR2_KERNEL_HEADERS_5_16
> + bool "kernel headers version 5.16.x are no longer supported"
> + select BR2_LEGACY
> + help
> + Version 5.16.x of the Linux kernel headers are no longer
> + maintained upstream and are now removed.
> +
> config BR2_KERNEL_HEADERS_4_4
> bool "kernel headers version 4.4.x are no longer supported"
> select BR2_LEGACY
> diff --git a/linux/linux.hash b/linux/linux.hash
> index 2a96eef8d3..3190813a0c 100644
> --- a/linux/linux.hash
> +++ b/linux/linux.hash
> @@ -1,6 +1,5 @@
> # From https://www.kernel.org/pub/linux/kernel/v5.x/sha256sums.asc
> sha256 22f67ef6b12ef6c0c0353be4b90b4bf4b9b18b858c16c346fa495b67ec718c99 linux-5.17.7.tar.xz
> -sha256 d8060dc88f862baaae66b42a2dbc12298ed667c698eb5c55617a7786ee47bf25 linux-5.16.20.tar.xz
> sha256 888641634f9e0e38cd0efcfec92ea3c126d381b24a514740d3fe3dc9988fd7ad linux-5.15.39.tar.xz
> sha256 f5e417b32f89318b6d0a230109a592ffd68997817463dc4692fa49ec7fe42f71 linux-5.10.115.tar.xz
> sha256 0d16d343956d311e3f4ab3f032fd626d8e6b67c0db94edd32f561407d374f2a0 linux-5.4.193.tar.xz
> --
> 2.30.2
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-13 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 14:42 [Buildroot] [PATCH 1/4] {linux, linux-headers}: bump 4.{9, 14, 19}.x / 5.{4, 10, 15}.x series Peter Korsgaard
2022-05-13 14:42 ` [Buildroot] [PATCH 2/4] {toolchain, linux-headers}: add support for 5.17.x headers Peter Korsgaard
2022-05-13 16:32 ` Yann E. MORIN
2022-05-13 14:42 ` [Buildroot] [PATCH 3/4] package/linux-headers: drop 5.16.x option Peter Korsgaard
2022-05-13 16:36 ` Yann E. MORIN [this message]
2022-05-13 14:42 ` [Buildroot] [PATCH 4/4] {linux,linux-headers}: default to 5.17.x Peter Korsgaard
2022-05-13 16:34 ` [Buildroot] [PATCH 4/4] {linux, linux-headers}: " Yann E. MORIN
2022-05-13 16:55 ` Peter Korsgaard
2022-05-13 20:35 ` Arnout Vandecappelle
2022-05-13 16:32 ` [Buildroot] [PATCH 1/4] {linux, linux-headers}: bump 4.{9, 14, 19}.x / 5.{4, 10, 15}.x series Yann E. MORIN
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=20220513163639.GR1597494@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=peter@korsgaard.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 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.