DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jan Blunck <jblunck@infradead.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce API changes to implement the bus model
Date: Mon, 13 Feb 2017 22:53:07 +0100	[thread overview]
Message-ID: <CALe+Z00nro6MAxwtHxnvq6CF_zeDiffC-YANkPLhU5gAD20+8g@mail.gmail.com> (raw)
In-Reply-To: <1487002834-27996-1-git-send-email-thomas.monjalon@6wind.com>

On Mon, Feb 13, 2017 at 5:20 PM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> The new bus model has been proposed in 17.02 without being used.
> The big rework should happen in 17.05.
>
> Suggested-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index f0b5329..8b66407 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -13,10 +13,14 @@ Deprecation Notices
>    has exposed, like the way we have done with uio-pci-generic. This change
>    targets release 17.05.
>
> -* ``eth_driver`` is planned to be removed in 17.02. This currently serves as
> +* The PCI and VDEV subsystems will be converted as drivers of the new bus model.
> +  It will imply some EAL API changes in 17.05.
> +
> +* ``eth_driver`` is planned to be removed in 17.05. This currently serves as
>    a placeholder for PMDs to register themselves. Changes for ``rte_bus`` will
>    provide a way to handle device initialization currently being done in
> -  ``eth_driver``.
> +  ``eth_driver``. Similarly, ``rte_pci_driver`` is planned to be removed from
> +  ``rte_cryptodev_driver`` in 17.05.
>
>  * ethdev: an API change is planned for 17.02 for the function
>    ``_rte_eth_dev_callback_process``. In 17.02 the function will return an ``int``
> --
> 2.7.0
>

Acked-by: Jan Blunck <jblunck@infradead.org>

  reply	other threads:[~2017-02-13 21:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 11:55 [dpdk-dev] [PATCH] doc: add deprecation note for rework of PCI in EAL Shreyansh Jain
2017-02-13 12:00 ` Shreyansh Jain
2017-02-13 14:44   ` Thomas Monjalon
2017-02-13 16:20     ` [dpdk-dev] [PATCH v2] doc: announce API changes to implement the bus model Thomas Monjalon
2017-02-13 21:53       ` Jan Blunck [this message]
2017-02-14  0:09         ` Hemant Agrawal
2017-02-14  0:33       ` Mcnamara, John
2017-02-14 18:57       ` Thomas Monjalon
2017-02-13 21:56   ` [dpdk-dev] [PATCH] doc: add deprecation note for rework of PCI in EAL Jan Blunck
2017-02-14  5:18     ` Shreyansh Jain

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=CALe+Z00nro6MAxwtHxnvq6CF_zeDiffC-YANkPLhU5gAD20+8g@mail.gmail.com \
    --to=jblunck@infradead.org \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).