From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 3/3] linux-headers: drop old unsupported 4.x versions
Date: Thu, 4 Oct 2018 21:45:12 +0200 [thread overview]
Message-ID: <20181004194512.GA2869@scaer> (raw)
In-Reply-To: <20180824230233.7a7e0a24@windsurf>
Thomas, Bernd, All,
On 2018-08-24 23:02 +0200, Thomas Petazzoni spake thusly:
> Hello,
>
> On Fri, 24 Aug 2018 20:41:33 +0200, Bernd Kuhls wrote:
> > These versions received their last updated more than three months ago
> > and are no longer supported according to
> > https://www.kernel.org/category/releases.html, so drop them and add
> > legacy entries.
> >
> > Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> > ---
> > Config.in.legacy | 53 ++++++++++++++++++++++++++++
> > package/linux-headers/Config.in.host | 25 -------------
> > 2 files changed, 53 insertions(+), 25 deletions(-)
> >
> > diff --git a/Config.in.legacy b/Config.in.legacy
> > index 29d5b6adcc..8c61d803da 100644
> > --- a/Config.in.legacy
> > +++ b/Config.in.legacy
> > @@ -142,6 +142,59 @@ comment "unpredictable ways. "
> > comment "----------------------------------------------------"
> > endif
> >
> > +###############################################################################
> > +comment "Legacy options removed in 2018.11"
> > +
> > +config BR2_KERNEL_HEADERS_4_10
> > + bool "kernel headers version 4.10.x are no longer supported"
> > + select BR2_KERNEL_HEADERS_4_14
>
> I think it makes more sense to automatically select some *older* kernel
> headers.
Except it is not allowed to select a choice entry anyway.
I'll send a patch removing the selects, since they do not work...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-10-04 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 18:41 [Buildroot] [PATCH/next 1/3] linux-headers: bump 4.{4, 9, 14, 17, 18}.x series Bernd Kuhls
2018-08-24 18:41 ` [Buildroot] [PATCH/next 2/3] linux: bump default to version 4.18.5 Bernd Kuhls
2018-08-24 21:03 ` Thomas Petazzoni
2018-08-24 18:41 ` [Buildroot] [PATCH/next 3/3] linux-headers: drop old unsupported 4.x versions Bernd Kuhls
2018-08-24 21:02 ` Thomas Petazzoni
2018-08-25 7:21 ` Bernd Kuhls
2018-09-02 8:07 ` Peter Korsgaard
2018-10-04 19:45 ` Yann E. MORIN [this message]
2018-08-24 21:00 ` [Buildroot] [PATCH/next 1/3] linux-headers: bump 4.{4, 9, 14, 17, 18}.x series Thomas Petazzoni
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=20181004194512.GA2869@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox