DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
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 18:13:13 +0200	[thread overview]
Message-ID: <5360265.dumfJixkPq@thomas> (raw)
In-Reply-To: <15237420.V5B86MhjE2@thomas>

13/07/2022 11:11, Thomas Monjalon:
> 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 <thomas@monjalon.net>
> > > 
> > > 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.

I've sent a new deprecation which updates Ferruh's one,
and squash parts of this one about the example:
https://patches.dpdk.org/project/dpdk/patch/20220713161047.121805-1-thomas@monjalon.net/

Please review quickly.



      reply	other threads:[~2022-07-13 16:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 16:50 Bruce Richardson
2022-07-01  2:17 ` Xia, Chenbo
2022-07-01  8:18 ` David Marchand
2022-07-12 11:50   ` Jerin Jacob
2022-07-12 14:17 ` Thomas Monjalon
2022-07-13  5:52   ` Andrew Rybchenko
2022-07-13  8:14   ` Bruce Richardson
2022-07-13  9:11     ` Thomas Monjalon
2022-07-13 16:13       ` Thomas Monjalon [this message]

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=5360265.dumfJixkPq@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=jerinj@marvell.com \
    /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).