DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, thomas@monjalon.net, grive@u256.net
Subject: Re: [dpdk-dev] [PATCH] doc: announce kernel driver enum removal
Date: Tue, 4 Aug 2020 15:29:38 +0100	[thread overview]
Message-ID: <20200804142938.GC1704@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20200804140752.8773-1-david.marchand@redhat.com>

On Tue, Aug 04, 2020 at 04:07:52PM +0200, David Marchand wrote:
> rte_kernel_driver is only used by the PCI subsystem and has polluted
> ethdev for no reason.
> Hide it in the PCI bus driver.
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 7 +++++++
>  1 file changed, 7 insertions(+)
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 9f73297173..6e86963c39 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -81,6 +81,13 @@ Deprecation Notices
>    With this removal, there won't be a need for the mentioned workaround which
>    will be reverted.
> +* pci: The ``rte_kernel_driver`` enum defined in rte_dev.h will be made private
> +  to the PCI subsystem as it is used only by the PCI bus driver and PCI
> +  drivers.
> +  The associated field ``kdrv`` in the ethdev ``rte_eth_dev_data`` structure
> +  will be removed as it gave no useful abstracted information to the
> +  applications and had no user (neither internal nor external).
> +
>  * ethdev: Split the ``struct eth_dev_ops`` struct to hide it as much as possible
>    will be done in 20.11.
>    Currently the ``struct eth_dev_ops`` struct is accessible by the application
> -- 

Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  reply	other threads:[~2020-08-04 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04 14:07 David Marchand
2020-08-04 14:29 ` Bruce Richardson [this message]
2020-08-04 14:44   ` Gaëtan Rivet
2020-08-05 23:16     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200804142938.GC1704@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=grive@u256.net \
    --cc=thomas@monjalon.net \


* 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).