From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] doc: update oldest supported kernel Date: Sun, 12 Nov 2017 05:30:36 +0100 Message-ID: <30826506.x33gGObbU7@xps> References: <20170926071712.25009-1-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Stephen Hemminger Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id A98DD1B25E for ; Sun, 12 Nov 2017 07:58:50 +0100 (CET) In-Reply-To: <20170926071712.25009-1-stephen@networkplumber.org> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 > --- > 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.