From: Olivier Matz <olivier.matz@6wind.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: jerinj@marvell.com, 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>,
thomas@monjalon.net, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH v3] doc: announce the removal of RTE_KDRV_NONE based probe
Date: Tue, 26 May 2020 16:44:44 +0200 [thread overview]
Message-ID: <20200526144444.GC2554@platinum> (raw)
In-Reply-To: <ad6cf52a-c391-145d-f81c-ced243d3c600@redhat.com>
On Mon, May 25, 2020 at 10:20:29AM +0200, Maxime Coquelin wrote:
>
>
> On 5/25/20 10:15 AM, jerinj@marvell.com wrote:
> > From: Jerin Jacob <jerinj@marvell.com>
> >
> > In order to optimize the DPDK PCI enumeration management, RTE_KDRV_NONE
> > based device driver probing will be removed in v20.08.
> > The legacy virtio is the only consumer of RTE_KDRV_NONE based
> > device driver probe scheme.
> > The legacy virtio support will be available through existing VFIO/UIO
> > based kernel driver scheme.
> > More details at http://patches.dpdk.org/patch/69351/
> >
> > Cc: maxime.coquelin@redhat.com
> > Cc: david.marchand@redhat.com
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> > ---
> > doc/guides/rel_notes/deprecation.rst | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> > index 2d11bae93..c7fb368ff 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -132,3 +132,11 @@ Deprecation Notices
> > Python 2 support will be completely removed in 20.11.
> > In 20.08, explicit deprecation warnings will be displayed when running
> > scripts with Python 2.
> > +
> > +* pci: Remove ``RTE_KDRV_NONE`` based device driver probing.
> > + In order to optimize the DPDK PCI enumeration management, ``RTE_KDRV_NONE``
> > + based device driver probing will be removed in v20.08.
> > + 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.
> > + More details at http://patches.dpdk.org/patch/69351/
> >
>
> Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
next prev parent reply other threads:[~2020-05-26 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 14:07 [dpdk-dev] [PATCH] doc: announce the deprecation of legacy virtio support jerinj
2020-05-24 23:44 ` Thomas Monjalon
2020-05-25 5:37 ` Jerin Jacob
2020-05-25 5:46 ` [dpdk-dev] [PATCH v2] doc: announce the removal " jerinj
2020-05-25 7:33 ` Maxime Coquelin
2020-05-25 7:52 ` Jerin Jacob
2020-05-25 8:15 ` [dpdk-dev] [PATCH v3] doc: announce the removal of RTE_KDRV_NONE based probe jerinj
2020-05-25 8:20 ` Maxime Coquelin
2020-05-26 14:44 ` Olivier Matz [this message]
2020-05-26 15:04 ` 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=20200526144444.GC2554@platinum \
--to=olivier.matz@6wind.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).