From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH] doc: update oldest supported kernel
Date: Sun, 12 Nov 2017 05:30:36 +0100 [thread overview]
Message-ID: <30826506.x33gGObbU7@xps> (raw)
In-Reply-To: <20170926071712.25009-1-stephen@networkplumber.org>
26/09/2017 09:17, Stephen Hemminger:
> The DPDK needs to stay up to date with current LTS Linux kernel support.
> If the kernel is older than LTS it is likely to be insecure and buggy.
> Therefore only require DPDK to work on oldest LTS kernel.
>
> If distribution vendors want to support DPDK on older kernels, that is
> their choice. But the upstream source does not need to be cluttered
> with support for this.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> doc/guides/linux_gsg/sys_reqs.rst | 4 +++-
[...]
> **Required:**
>
> -* Kernel version >= 2.6.34
> +* Kernel version >= 3.2.93
I think we should not specify any minor number. 3.2 is enough.
It would make more sense to change this constraint at the beginning
of a release cycle.
next prev parent reply other threads:[~2017-11-12 6:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 7:17 [PATCH] doc: update oldest supported kernel Stephen Hemminger
2017-10-13 15:49 ` Mcnamara, John
2017-10-13 15:55 ` Luca Boccassi
2017-10-13 15:54 ` Luca Boccassi
2017-11-12 4:30 ` Thomas Monjalon [this message]
2017-11-15 15:55 ` Ferruh Yigit
2017-11-28 22:02 ` [PATCH v2] doc: update oldest supported kernel in Linux guide Thomas Monjalon
2017-12-12 14:20 ` Kovacevic, Marko
2017-12-15 14:24 ` 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=30826506.x33gGObbU7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.