From: Arnout Vandecappelle <arnout@mind.be>
To: Peter Korsgaard <peter@korsgaard.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/4] {linux, linux-headers}: default to 5.17.x
Date: Fri, 13 May 2022 22:35:04 +0200 [thread overview]
Message-ID: <7c474ae0-2a57-0c3f-56e4-9c7017bc84ea@mind.be> (raw)
In-Reply-To: <87lev58j8l.fsf@dell.be.48ers.dk>
On 13/05/2022 18:55, Peter Korsgaard wrote:
>>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>
> > Peter, All,
> > On 2022-05-13 16:42 +0200, Peter Korsgaard spake thusly:
> >> 5.15.x is getting quite old, so default to 5.17.x instead.
>
> > But 5.15 is a longterm kernel, while 5.17 will probably not be.
>
> True, but we normally default to the latest kernel, I just kept it for
> 5.15 for the LTS release.
FWIW, +1 to that philosophy.
Regards,
Arnout
>
> > Also, see below...
>
> >> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> >> ---
> > [--SNIP--]
> >> diff --git a/package/linux-headers/Config.in.host b/package/linux-headers/Config.in.host
> >> index 5ff616fb34..859f772624 100644
> >> --- a/package/linux-headers/Config.in.host
> >> +++ b/package/linux-headers/Config.in.host
> > [--SNIP--]
> >> @@ -56,10 +56,6 @@ config BR2_KERNEL_HEADERS_5_15
> >> bool "Linux 5.15.x kernel headers"
> >> select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_15
> >>
> >> -config BR2_KERNEL_HEADERS_5_16
> >> - bool "Linux 5.16.x kernel headers"
> >> - select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_16
>
> > Did you forget to squash this hunk...
>
> Ups, indeed. Will fix.
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-13 20:35 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
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 [this message]
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=7c474ae0-2a57-0c3f-56e4-9c7017bc84ea@mind.be \
--to=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=peter@korsgaard.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.