From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: ci@dpdk.org, dev@dpdk.org,
Stephen Hemminger <stephen@networkplumber.org>,
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>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: Re: [PATCH v2 2/2] kni: remove deprecated kernel network interface
Date: Mon, 7 Aug 2023 09:15:10 +0200 [thread overview]
Message-ID: <CAJFAV8xz4vcG_wbLzLCGb4cmqBpLa4VDFnjW3gLcP_+dCSZHbw@mail.gmail.com> (raw)
In-Reply-To: <ZMz8T096ecOjvwIo@bricha3-MOBL.ger.corp.intel.com>
On Fri, Aug 4, 2023 at 3:26 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
> > With this removal, there is no remaining out of tree Linux kernel module
> > to compile/test in DPDK sources. This means that jobs (like the one in
> > UNH lab that was compile-testing KNI against the latest Linux kernel
> > sources) can be disabled.
> >
> > Important note: this mail does not ask for any change to LTS releases
> > testing. If KNI was built and tested with LTS releases, you should
> > continue to do so.
> >
> Given that there are no linux modules left, can we consider changing the
> default setting of "enable_kmods" from "no" to "yes". For FreeBSD there are
> no in-tree modules that can support DPDK, so the kernel modules for that OS
> should always be built. The only reason for it being disabled was Linux,
> but that seems unnecessary now.
This seems ok to me.
--
David Marchand
next prev parent reply other threads:[~2023-08-07 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230801160500.67480-1-stephen@networkplumber.org>
[not found] ` <20230801160500.67480-3-stephen@networkplumber.org>
2023-08-04 13:19 ` David Marchand
2023-08-04 13:25 ` Bruce Richardson
2023-08-07 7:15 ` David Marchand [this message]
2023-08-09 14:20 ` Patrick Robb
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=CAJFAV8xz4vcG_wbLzLCGb4cmqBpLa4VDFnjW3gLcP_+dCSZHbw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenbo.xia@intel.com \
--cc=ci@dpdk.org \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--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 \
--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).