From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2FED0A0032; Wed, 13 Jul 2022 11:11:22 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 11CAD42847; Wed, 13 Jul 2022 11:11:22 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id A6FBA4069D for ; Wed, 13 Jul 2022 11:11:20 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 256CE5C0172; Wed, 13 Jul 2022 05:11:20 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 13 Jul 2022 05:11:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1657703480; x= 1657789880; bh=tKINbnFT/+wLYifMR7LWfGuYFttbRSTjW58G4aZBTk0=; b=H FgakmQKdsf8LZNkN5nX74rXad3lHKrAAApRAe4niybQtrOOzFiy11anzNMfTviFx kztG1KKOH6XyfYyWCObECxrjpnrf3HFBe86weo4T8fGVZn8FpAXgXnjusoZEuSUm ifAiMKb6pQKMBHo3d7ZBHPNQlEzrGdoZnPsv5IPVIcoU6o4l5jJuy2HP7GHHSekl /2IvlEQtpfVOsEnYvBbRPLOvaJw846S8ZELWp8aLAKeog5OMHEs9Z3aUfL2zGK7L Kmem6GS2M/c+13TnPlkv4KVn9at5Axhqo/jvhWqs9OvV4rRJwmE5Fv3QoDTmGif+ +5XxWbtJRhcArJX/72vzQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1657703480; x= 1657789880; bh=tKINbnFT/+wLYifMR7LWfGuYFttbRSTjW58G4aZBTk0=; b=1 mMBLOnDF8UnCFoFpmb32bdPlDAsDVjYSqoOUZ6Jc+4lFqqHllS24kCQpRW9hhXhj soUQYs99jPJlMuYNUo97dRvxzsot90Eq9vJzXNHsOHSSC7ldv9ZLxEhTGWO/NC46 XCW4qiUEoT8xQK6Nt7uYnENkx3JEVqTQFDVpdLiAwd1wDbsQp6jLCYA5nRQ0TVlY rzg4URo5CDTCNcSM6GO6kTE3iZ9dzm/yIDsQbJFrcr9Fq8gW2keP2aN7ugZRyUjl UsnLxEgNmOWeYetnWZRdCN2Btj1tZM9+9ma0W4ce1Rn2SmqZ+07KtvZ4pM0SgvoU inJlf9ggaQ62jc079Qs1w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudejjedgudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 13 Jul 2022 05:11:19 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson Cc: dev@dpdk.org, chenbo.xia@intel.com, david.marchand@redhat.com, jerinj@marvell.com, ferruh.yigit@amd.com Subject: Re: [PATCH] doc: add deprecation notice for kni example Date: Wed, 13 Jul 2022 11:11:17 +0200 Message-ID: <15237420.V5B86MhjE2@thomas> In-Reply-To: References: <20220630165031.79183-1-bruce.richardson@intel.com> <2968096.U7Z2iKR65Z@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 13/07/2022 10:14, Bruce Richardson: > On Tue, Jul 12, 2022 at 04:17:31PM +0200, Thomas Monjalon wrote: > > 30/06/2022 18:50, Bruce Richardson: > > > +* examples/kni: The ``kni`` kernel module and library are not recommended for use by new applications - > > > + other technologies such as virtio-user are recommended instead. > > > + Because of this, the example application for kni is deprecated and will be removed in a future release. > > > > Acked-by: Thomas Monjalon > > > > I think it would have been better to give a precise timeline. > > > I intentionally left it vague in case we decided to defer removal for a > release or anything. However, feel free to replace "in a future" release > with "in 22.11 release" on apply if you like. I won't do such change myself, too much critical.