From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH] doc: add kernel version deprecation notice
Date: Wed, 31 Jan 2018 07:27:09 -0800 [thread overview]
Message-ID: <20180131152709.13853-1-stephen@networkplumber.org> (raw)
Notify users of upcoming change in kernel requirement.
Encourage users to use current LTS kernel version.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
doc/guides/rel_notes/deprecation.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index d59ad598862b..31d64b27ba17 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -59,3 +59,9 @@ Deprecation Notices
be added between the producer and consumer structures. The size of the
structure and the offset of the fields will remain the same on
platforms with 64B cache line, but will change on other platforms.
+
+* linux: Linux kernel version 3.2 (which is the current minimum required
+ version for the DPDK) will be end of life in May 2018. Therefore the planned
+ minimum required kernel version for DPDK 18.5 will be next oldest Long
+ Term Stable (LTS) version which is 3.10. The recommended kernel version is
+ the latest LTS kernel which currently is 4.14.
--
2.15.1
next reply other threads:[~2018-01-31 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 15:27 Stephen Hemminger [this message]
2018-02-13 23:58 ` Thomas Monjalon
2018-02-14 10:26 ` Olivier Matz
2018-02-14 10:31 ` Luca Boccassi
2018-02-14 10:38 ` Thomas Monjalon
2018-02-14 10:38 ` Maxime Coquelin
2018-02-14 10:54 ` Luca Boccassi
2018-02-14 11:44 ` Bruce Richardson
2018-02-14 18:08 ` Stephen Hemminger
2018-02-15 9:26 ` Bruce Richardson
2018-02-15 14:15 ` Aaron Conole
2018-05-24 20:53 ` Thomas Monjalon
2018-02-14 10:33 ` Maxime Coquelin
2018-11-24 18:44 ` [dpdk-dev] [PATCH v2] doc: announce Linux support change 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=20180131152709.13853-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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).