From: Jerin Jacob <jerinjacobk@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
Ray Kinsella <mdr@ashroe.eu>,
Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] bus/pci: optimize bus scan
Date: Wed, 24 Jun 2020 14:23:51 +0530 [thread overview]
Message-ID: <CALBAE1Psuw4DLa6RXO-HePZu=X9hsyaoVT15S+pkOvFA8rnN5A@mail.gmail.com> (raw)
In-Reply-To: <2477629.211Q8sjVOW@thomas>
On Wed, Jun 17, 2020 at 3:09 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 10/06/2020 13:50, jerinj@marvell.com:
> > From: Jerin Jacob <jerinj@marvell.com>
> >
> > In order to optimize the PCI management, RTE_KDRV_NONE based
> > device driver probing removed by not adding them to list in
> > the scan phase.
> >
> > The legacy virtio is the only consumer of RTE_KDRV_NONE based device
> > driver probe scheme. The legacy virtio support will be available
> > through the existing VFIO/UIO based kernel driver scheme.
> >
> > This patch also removes the deprecation notice for the same.
> >
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> > ---
> > doc/guides/rel_notes/deprecation.rst | 8 --------
> > drivers/bus/pci/linux/pci.c | 25 +++----------------------
> > 2 files changed, 3 insertions(+), 30 deletions(-)
>
> I suggest adding a note in Removed Items:
> http://git.dpdk.org/dpdk/tree/doc/guides/rel_notes/release_20_08.rst#n66
Sure. I will send the v2.
>
>
>
next prev parent reply other threads:[~2020-06-24 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 11:50 jerinj
2020-06-16 21:39 ` Thomas Monjalon
2020-06-24 8:53 ` Jerin Jacob [this message]
2020-06-24 11:46 ` [dpdk-dev] [PATCH v2] " jerinj
2020-06-24 21:52 ` Thomas Monjalon
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='CALBAE1Psuw4DLa6RXO-HePZu=X9hsyaoVT15S+pkOvFA8rnN5A@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.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).