From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Subject: Re: [PATCH v2] examples/kni: remove deprecated kni example
Date: Mon, 03 Oct 2022 19:09:09 +0200 [thread overview]
Message-ID: <3612643.TKLx3GfHUD@thomas> (raw)
In-Reply-To: <20221003094715.4d4a8afa@hermes.local>
03/10/2022 18:47, Stephen Hemminger:
> On Mon, 03 Oct 2022 18:11:08 +0200
> Thomas Monjalon <thomas@monjalon.net> wrote:
>
> > 20/09/2022 17:51, Bruce Richardson:
> > > As part of the agreed process for deprecating KNI in DPDK, the example
> > > app is scheduled for removal as part of the 22.11 release.
> > >
> > > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > > ---
> > > V2: Correct old release note links to KNI guide by referencing older doc
> >
> > Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> > Acked-by: Thomas Monjalon <thomas@monjalon.net>
> >
> > Applied, thanks.
>
> What about many of the other places that refer or use KNI?
> The packet framework, port library and ip_pipeline all have kni hooks.
This was only removing the example.
Someone needs to work on the other parts.
And we should add some warning at build time and runtime for KNI
in this release 22.11, as announced in the deprecation page.
Volunteer?
prev parent reply other threads:[~2022-10-03 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 15:14 [PATCH] " Bruce Richardson
2022-09-20 15:25 ` Stephen Hemminger
2022-09-20 15:51 ` [PATCH v2] " Bruce Richardson
2022-10-03 16:11 ` Thomas Monjalon
2022-10-03 16:47 ` Stephen Hemminger
2022-10-03 17:09 ` 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=3612643.TKLx3GfHUD@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--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 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).