From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK kernel requirements
Date: Wed, 31 Jan 2018 01:45:23 +0100 [thread overview]
Message-ID: <4318505.uD02kM9JbA@xps> (raw)
In-Reply-To: <20180130163141.08109975@xeon-e3>
31/01/2018 01:31, Stephen Hemminger:
> Where is the minimum Linux kernel version requirement documented.
>
> For 18.02 the version should be kernel version 3.2 or greater.
It is your patch:
http://dpdk.org/commit/90f3229fc0
> Since 3.2 will EOL if May, for 18.05 the requirement will advance to next LTS kernel
> which is 3.16. It would be good to put in a deprecation warning about that in 18.02
> release; for warned is for armed.
Yes, feel free to write a deprecation notice in
doc/guides/rel_notes/deprecation.rst
> Since 3.16 is good until April 2020, it will be several more releases until the
> horizon can be moved again.
OK thanks for the info.
prev parent reply other threads:[~2018-01-31 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 0:31 Stephen Hemminger
2018-01-31 0:45 ` Thomas Monjalon [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=4318505.uD02kM9JbA@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).