From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, 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>,
david.marchand@redhat.com
Subject: Re: [PATCH v2] kni: remove deprecated kernel network interface
Date: Mon, 31 Jul 2023 23:27:59 +0200 [thread overview]
Message-ID: <16742583.Ash8RoxBsO@thomas> (raw)
In-Reply-To: <20230731141219.17a80c57@hermes.local>
31/07/2023 23:12, Stephen Hemminger:
> On Mon, 31 Jul 2023 10:40:35 +0200
> Thomas Monjalon <thomas@monjalon.net> wrote:
>
> > > 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?
> >
> > No we must support it until it is removed.
> > You should either disable or remove KNI from the port library.
>
> I just removed those calls from port library.
>
> One reason that KNI can't be isolated into a separate kmod repo
> is that it has components such as lib/kni that were being shared
> in several places like port, examples, and tests.
Yes you're right.
next prev parent reply other threads:[~2023-07-31 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 22:54 [PATCH] kni: remove deprecated kernel network interface Stephen Hemminger
2023-07-30 2:12 ` [PATCH v2] " Stephen Hemminger
2023-07-30 17:12 ` Stephen Hemminger
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 [this message]
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=16742583.Ash8RoxBsO@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenbo.xia@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.