From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/4] Support Linux 4.20
Date: Thu, 10 Jan 2019 15:47:22 +0100 [thread overview]
Message-ID: <87woncr2md.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <877efnpa7x.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Wed, 02 Jan 2019 12:31:14 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
>> Hello,
>> On Tue, 01 Jan 2019 22:58:44 +0100, Peter Korsgaard wrote:
>>> With 2019.02 becoming our next LTS and 4.20 NOT a LTS release, I wonder
>>> if it would make sense to still default to 4.19.x instead of 4.20.x?
>> Yes, that probably make sense. But in this case, we would need to get
>> in touch with the kernel folks to get the net_tstamp.h fix in -stable.
>> It has the Fixes: tag, but it still hasn't been backported to
>> 4.19-stable.
> Ok. The last few 4.19.x releases did not contain any net/ fixes, perhaps
> that will fixed now the holidays are over.
This has indeed been fixed in 4.19.14. I have sent a patch to change our
default linux / linux-headers version back to 4.19.x:
https://patchwork.ozlabs.org/patch/1022974/
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-01-10 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 17:52 [Buildroot] [PATCH v2 0/4] Support Linux 4.20 Thomas Petazzoni
2018-12-31 17:52 ` [Buildroot] [PATCH v2 1/4] toolchain: add necessary options to support 4.20 kernel headers Thomas Petazzoni
2018-12-31 17:52 ` [Buildroot] [PATCH v2 2/4] package/linux-headers: add support for Linux " Thomas Petazzoni
2018-12-31 17:52 ` [Buildroot] [PATCH v2 3/4] linux: add support for Linux 4.20 Thomas Petazzoni
2018-12-31 17:52 ` [Buildroot] [PATCH v2 4/4] toolchain/toolchain-external-custom: support Linux 4.20 kernel headers Thomas Petazzoni
2019-01-01 21:58 ` [Buildroot] [PATCH v2 0/4] Support Linux 4.20 Peter Korsgaard
2019-01-02 8:16 ` Thomas Petazzoni
2019-01-02 11:31 ` Peter Korsgaard
2019-01-02 12:50 ` Thomas Petazzoni
2019-01-10 14:47 ` 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=87woncr2md.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