From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>,
bruce.richardson@intel.com, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH] doc: update minimum supported kernel
Date: Tue, 16 Mar 2021 11:52:52 +0000 [thread overview]
Message-ID: <c10cc1d6-37c4-d229-edfd-536a2a956e45@intel.com> (raw)
In-Reply-To: <5834638.C097LPqU2r@thomas>
On 3/16/2021 10:59 AM, Thomas Monjalon wrote:
> 03/03/2021 19:28, Stephen Hemminger:
>> The DPDK project is only committed to supporting upstream kernel
>> versions that are still in support.
>> The 3.16 kernel has reached End Of Life (in June 2020).
>> The next LTS kernel is 4.19 and is supported until December 2024.
>>
>> This does not change the existing policy that distribution kernels
>> that are older are still supported.
>>
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>> ---
>> **Required:**
>>
>> -* Kernel version >= 3.16
>> +* Kernel version >= 4.19
>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
>
>
No objection, but I see 4.4 is the oldest LTS, and there are a few in the middle
till 4.19 [1]. Is 4.19 selected specially?
And what about adding a note to say oldest LTS kernel version is supported?
[1] https://www.kernel.org/category/releases.html
next prev parent reply other threads:[~2021-03-16 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 18:28 Stephen Hemminger
2021-03-16 10:59 ` Thomas Monjalon
2021-03-16 11:52 ` Ferruh Yigit [this message]
2021-03-16 12:54 ` Thomas Monjalon
2021-03-16 15:50 ` Stephen Hemminger
2021-04-19 22:06 ` [dpdk-dev] [PATCH v2] " Stephen Hemminger
2021-05-19 16:37 ` Thomas Monjalon
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=c10cc1d6-37c4-d229-edfd-536a2a956e45@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
--cc=thomas@monjalon.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;
as well as URLs for NNTP newsgroup(s).