From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
Jerin Jacob <jerinjacobk@gmail.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
Zhihong Wang <zhihong.wang@intel.com>,
"Ye, Xiaolong" <xiaolong.ye@intel.com>,
Harman Kalra <hkalra@marvell.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>, Gaetan Rivet <grive@u256.net>,
Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] bus/pci: optimize pci device probe
Date: Wed, 6 May 2020 13:37:38 +0200 [thread overview]
Message-ID: <CAJFAV8wi0Nb8u6MyNEoR3J26sT2e4XTxh3COBvkayzLtsbPpFQ@mail.gmail.com> (raw)
In-Reply-To: <CALBAE1OGG2Dw06bW9Edh4N1-mPHjHcTtC=om3HHt6+VAqWVo7Q@mail.gmail.com>
On Wed, May 6, 2020 at 12:51 PM Jerin Jacob <jerinjacobk@gmail.com> wrote:
> > > 3) if yes, Please fix RTE_PMD_REGISTER_KMOD_DEP(net_virtio, "* igb_uio
> > > | uio_pci_generic | vfio-pci");
> >
> > While support gets removed, what about:
> >
> > RTE_PMD_REGISTER_KMOD_DEP(net_virtio, "* igb_uio | uio_pci_generic |
> > vfio-pci | none"); ?
>
> +1
I know some scripts rely on such info to modprobe and bind the devices
based on such info.
So "none" does not make sense, there is no "none" kmod.
Since we want to deprecate this capability, let's not advertise this.
--
David Marchand
next prev parent reply other threads:[~2020-05-06 11:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 17:38 jerinj
2020-04-26 18:08 ` Thomas Monjalon
2020-04-26 18:41 ` Jerin Jacob
2020-04-26 20:06 ` Thomas Monjalon
2020-04-27 17:59 ` Jerin Jacob
2020-04-28 8:50 ` David Marchand
2020-04-28 9:34 ` Jerin Jacob
2020-05-05 15:50 ` Jerin Jacob
2020-05-05 16:16 ` David Marchand
2020-05-06 6:34 ` Maxime Coquelin
2020-05-06 6:43 ` Jerin Jacob
2020-05-06 7:52 ` Maxime Coquelin
2020-05-06 10:51 ` Jerin Jacob
2020-05-06 11:37 ` David Marchand [this message]
2020-05-06 11:44 ` Maxime Coquelin
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=CAJFAV8wi0Nb8u6MyNEoR3J26sT2e4XTxh3COBvkayzLtsbPpFQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=olivier.matz@6wind.com \
--cc=thomas@monjalon.net \
--cc=xiaolong.ye@intel.com \
--cc=zhihong.wang@intel.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).