DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Thomas Monjalon (thomas.monjalon@6wind.com)"
	<thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce renaming of ethdev library
Date: Thu, 28 Jul 2016 11:29:29 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725836B8AAC4@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2025A9104@IRSMSX103.ger.corp.intel.com>



>
> The right name of ethdev should be dpdk_netdev. However:
> 1/ We are using rte_ prefix in the code and library names.
> 2/ The API uses rte_ethdev
 > That's why 16.11 will just have the rte_ prefix prepended to the
> library filename as every other libraries.
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
 > ---
 >  doc/guides/rel_notes/deprecation.rst | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index f502f86..7a55037 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -11,6 +11,9 @@ Deprecation Notices
>  * The log history is deprecated.
>    It is voided in 16.07 and will be removed in release 16.11.
>
> +* The ethdev library file will be renamed from libethdev.* to
> +librte_ethdev.*
> +  in release 16.11 in order to have a more consistent namespace.
> +
>  * The ethdev hotplug API is going to be moved to EAL with a
> notification
>    mechanism added to crypto and ethdev libraries so that hotplug
> is
> now
 >    available to both of them. This API will be stripped of the
> device arguments
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>

> 2.7.0

      parent reply	other threads:[~2016-07-28 11:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 16:22 Thomas Monjalon
2016-07-27 16:33 ` [dpdk-dev] " Jan Viktorin
2016-07-28  9:29   ` Christian Ehrhardt
2016-07-28  9:52     ` Thomas Monjalon
2016-07-28 17:37     ` Thomas Monjalon
     [not found] ` <B27915DBBA3421428155699D51E4CFE2025A902D@IRSMSX103.ger.corp.intel.com>
     [not found]   ` <2601191342CEEE43887BDE71AB97725836B8AAA2@irsmsx105.ger.corp.intel.com>
     [not found]     ` <B27915DBBA3421428155699D51E4CFE2025A9104@IRSMSX103.ger.corp.intel.com>
2016-07-28 11:29       ` Ananyev, Konstantin [this message]

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=2601191342CEEE43887BDE71AB97725836B8AAC4@irsmsx105.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.com \
    --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).