From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/linux-headers: drop obsolete 3.2.x / 4.{1, 16, 18}.x versions
Date: Wed, 02 Jan 2019 14:26:29 +0100 [thread overview]
Message-ID: <8736qbp4vu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190102135720.232e4f5f@windsurf> (Thomas Petazzoni's message of "Wed, 2 Jan 2019 13:57:20 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello,
> On Wed, 2 Jan 2019 12:11:40 +0100, Peter Korsgaard wrote:
>> According to https://www.kernel.org/category/releases.html, these kernel
>> versions are no longer supported, so drop them now that we have added 4.20.x
>>
>> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
>> ---
>> linux/linux.hash | 5 -----
>> package/linux-headers/Config.in.host | 23 -----------------------
>> 2 files changed, 28 deletions(-)
> We do have some Config.in.legacy handling for those options:
> $ grep KERNEL_HEADERS Config.in.legacy
> config BR2_KERNEL_HEADERS_4_10
> config BR2_KERNEL_HEADERS_4_11
> config BR2_KERNEL_HEADERS_4_12
> config BR2_KERNEL_HEADERS_4_13
> config BR2_KERNEL_HEADERS_4_15
> config BR2_KERNEL_HEADERS_4_17
> config BR2_KERNEL_HEADERS_3_4
> config BR2_KERNEL_HEADERS_3_10
> config BR2_KERNEL_HEADERS_3_12
> config BR2_KERNEL_HEADERS_4_8
> config BR2_KERNEL_HEADERS_3_18
> config BR2_KERNEL_HEADERS_4_7
> config BR2_KERNEL_HEADERS_4_6
> config BR2_KERNEL_HEADERS_4_5
> config BR2_KERNEL_HEADERS_3_14
> config BR2_KERNEL_HEADERS_4_3
> config BR2_KERNEL_HEADERS_4_2
> config BR2_KERNEL_HEADERS_4_0
> config BR2_KERNEL_HEADERS_3_19
> config BR2_KERNEL_HEADERS_3_17
> config BR2_KERNEL_HEADERS_3_16
> config BR2_KERNEL_HEADERS_3_0
> config BR2_KERNEL_HEADERS_3_11
> config BR2_KERNEL_HEADERS_3_13
> config BR2_KERNEL_HEADERS_3_15
> config BR2_KERNEL_HEADERS_3_8
> config BR2_KERNEL_HEADERS_3_6
> config BR2_KERNEL_HEADERS_3_7
> config BR2_KERNEL_HEADERS_SNAP
> config BR2_KERNEL_HEADERS_3_1
> config BR2_KERNEL_HEADERS_3_3
> config BR2_KERNEL_HEADERS_3_5
> Shouldn't we continue with the same process ?
Yes, certainly. I got interrupted while making this patch and completely
forgot about it again.
Will fix.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-01-02 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 11:11 [Buildroot] [PATCH] package/linux-headers: drop obsolete 3.2.x / 4.{1, 16, 18}.x versions Peter Korsgaard
2019-01-02 12:57 ` Thomas Petazzoni
2019-01-02 13:26 ` 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=8736qbp4vu.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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