From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v2] kni: remove deprecated kernel network interface
Date: Sun, 30 Jul 2023 10:12:59 -0700 [thread overview]
Message-ID: <20230730101259.433d4067@hermes.local> (raw)
In-Reply-To: <20230730021206.6381-1-stephen@networkplumber.org>
On Sat, 29 Jul 2023 19:12:05 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> Deprecation and removal was announced in 22.11.
> Make it so.
>
> Leave kernel/linux with empty directory because
> CI is trying to directly build it. At some later date,
> kernel/linux can be removed.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Want suggestions on this.
1. The release notes gets coding style warning because checkpatch
is checking that release note matches current release, and release number
hasn't change yet. Should I just wait?
2. The OVSrobot is looking into the port library to see the kni symbols.
But port is marked as deprecated already.
Perhaps we should just pull out port first?
next prev parent reply other threads:[~2023-07-30 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 22:54 [PATCH] " Stephen Hemminger
2023-07-30 2:12 ` [PATCH v2] " Stephen Hemminger
2023-07-30 17:12 ` Stephen Hemminger [this message]
2023-07-31 8:40 ` Thomas Monjalon
2023-07-31 15:13 ` Stephen Hemminger
2023-07-31 15:21 ` David Marchand
2023-07-31 15:35 ` Thomas Monjalon
2023-07-31 21:12 ` Stephen Hemminger
2023-07-31 21:27 ` Thomas Monjalon
2023-08-01 7:33 ` David Marchand
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=20230730101259.433d4067@hermes.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenbo.xia@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=kirankumark@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=thomas@monjalon.net \
/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).