From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/linux-headers: add support for Linux 5.1 kernel headers
Date: Mon, 08 Apr 2019 12:47:22 +0200 [thread overview]
Message-ID: <87sgushiyt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1406533656.445702.1554710793435.JavaMail.zimbra@kalray.eu> ("Clément Leger"'s message of "Mon, 8 Apr 2019 10:06:33 +0200 (CEST)")
>>>>> "Cl?ment" == Cl?ment Leger <cleger@kalray.eu> writes:
> Yes, that was the intended modification.
> But it can probably wait for the 5.1 release if needed.
Up to you. Either send a patch now just for _CUSTOM_5_1 and then another
once 5.1 is released or wait.
When we add 5.1 I think it makes sense to remove 4.20 as it is now EOL.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-04-08 10:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 7:01 [Buildroot] [PATCH 1/3] toolchain: add BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_1 Clément Leger
2019-04-04 7:01 ` [Buildroot] [PATCH 2/3] toolchain/toolchain-external-custom: support Linux 5.1 Clément Leger
2019-04-04 7:03 ` [Buildroot] [PATCH 3/3] package/linux-headers: add support for Linux 5.1 kernel headers Clément Leger
2019-04-07 7:13 ` Peter Korsgaard
2019-04-08 7:18 ` Clément Leger
2019-04-08 7:47 ` Peter Korsgaard
2019-04-08 8:06 ` Clément Leger
2019-04-08 10:47 ` Peter Korsgaard [this message]
2019-04-07 7:13 ` [Buildroot] [PATCH 2/3] toolchain/toolchain-external-custom: support Linux 5.1 Peter Korsgaard
2019-04-07 7:12 ` [Buildroot] [PATCH 1/3] toolchain: add BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_1 Peter Korsgaard
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=87sgushiyt.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