From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4F56120AC5; Sun, 12 Nov 2017 01:58:50 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 12 Nov 2017 01:58:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=R9fQmlTm1VfJHpnN9VLvCAu3vX iFGhlX0wGtAzK1BHk=; b=UEXCH7s9qmfQKYMM3Qjclk6qpPpMn3Jd/B5VseoOSr 093zrrqfiNiJtnJ2iVK0JXJzZ5faFC1ZfvrHiZGdPDHe+Ps9lx6mllQkE6tdNhmR qGux4sgZCvNPTJ4Nm0ShP5Db3cnyvMqEI/+vcW7rlXZATEeB2GXIBS3ptn6g5GW3 s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=R9fQml Tm1VfJHpnN9VLvCAu3vXiFGhlX0wGtAzK1BHk=; b=gjbt6GgHdWHFO9tW2TWKQ+ F+Jed791Nyr5zkO5mgXl7Nu7PHXw+Bs4XecZuM2G9LZEqS4bxaBiC3d2+scsodxl jvPWxaIdtQvOWdY903U28FFBmiuAw8rJZZu85Ppmc5+yZb+kELNxktw5Lc0H13oU d1PAHAFtDJ+YK1seaaFQFDAbN8aVb0dcKXSi6Fewwa1dZ/v04Uh9OxvLM+OvBZkk o8TFBpfm7vrLC3fHadbYWcUj3356g8wN6qviAhfvmgcc4YmHM066heGLouqXrTDi eiek6GyVbv5HGCQy2PjMt2fqicGxp13QqTjhmfHvNgvxUobmNbQNma9F0yXRhOQg == X-ME-Sender: Received: from xps.localnet (unknown [12.232.154.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 16CDC243F9; Sun, 12 Nov 2017 01:58:50 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org Date: Sun, 12 Nov 2017 05:30:36 +0100 Message-ID: <30826506.x33gGObbU7@xps> In-Reply-To: <20170926071712.25009-1-stephen@networkplumber.org> References: <20170926071712.25009-1-stephen@networkplumber.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: update oldest supported kernel X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2017 06:58:51 -0000 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.