From: Olivier Matz <olivier.matz@6wind.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: add kernel version deprecation notice
Date: Wed, 14 Feb 2018 11:26:47 +0100 [thread overview]
Message-ID: <20180214102647.tztob5mqoltdwldw@platinum> (raw)
In-Reply-To: <2393289.cND9ge7AvX@xps>
On Wed, Feb 14, 2018 at 12:58:34AM +0100, Thomas Monjalon wrote:
> 31/01/2018 16:27, Stephen Hemminger:
> > Notify users of upcoming change in kernel requirement.
> > Encourage users to use current LTS kernel version.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > ---
> > +* 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.
>
> We could print a warning at EAL init if kernel version does not satisfy the
> minimal requirement.
>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
next prev parent reply other threads:[~2018-02-14 10:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 15:27 Stephen Hemminger
2018-02-13 23:58 ` Thomas Monjalon
2018-02-14 10:26 ` Olivier Matz [this message]
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=20180214102647.tztob5mqoltdwldw@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--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).