From: Thomas Monjalon <thomas@monjalon.net>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: techboard@dpdk.org, dev@dpdk.org, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [dpdk-techboard] [PATCH] doc: note min required kernel version increase for 19.02
Date: Wed, 10 Oct 2018 14:11:32 +0200 [thread overview]
Message-ID: <1582218.eZnQbrohzq@xps> (raw)
In-Reply-To: <20181010094053.21616-1-ktraynor@redhat.com>
10/10/2018 11:40, Kevin Traynor:
> Updating docs to reflect decision made at the techboard
> that the min kernel version should be bumped from 3.2 to
> the latest longterm stable release (3.16), but that
> compatiblity for commonly used distribution kernels should
> be kept also.
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> +.. note::
> +
> + Kernel version 3.2 is no longer a kernel.org longterm stable kernel.For DPDK 19.02 the minimum
> + required kernel will be updated to the current kernel.org oldest longterm stable supported kernel
> + 3.16 or recent versions of common distributions, notably RHEL/CentOS 7.
On a style note, better to break lines after end of sentence,
or logically:
Kernel version 3.2 is no longer a kernel.org longterm stable kernel.
For DPDK 19.02 the minimum required kernel will be updated to
the current kernel.org oldest longterm stable supported kernel 3.16,
or recent versions of common distributions, notably RHEL/CentOS 7.
Except style,
Acked-by: Thomas Monjalon <thomas@monjalon.net>
next prev parent reply other threads:[~2018-10-10 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 9:40 [dpdk-dev] " Kevin Traynor
2018-10-10 10:07 ` [dpdk-dev] [dpdk-techboard] " Maxime Coquelin
2018-10-10 12:11 ` Thomas Monjalon [this message]
2018-10-10 14:14 ` [dpdk-dev] [PATCH v2] " Kevin Traynor
2018-11-18 23:57 ` 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=1582218.eZnQbrohzq@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=techboard@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).