From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: API change notice for librte_table
Date: Tue, 9 May 2017 16:34:23 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F01139734@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <1493749373-55709-1-git-send-email-cristian.dumitrescu@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Cristian Dumitrescu
> Sent: Tuesday, May 2, 2017 7:23 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: API change notice for librte_table
>
> Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index a3e7c72..ae937f5 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -81,3 +81,9 @@ Deprecation Notices
>
> - ``rte_crpytodev_scheduler_mode_get``, replaced by
> ``rte_cryptodev_scheduler_mode_get``
> - ``rte_crpytodev_scheduler_mode_set``, replaced by
> ``rte_cryptodev_scheduler_mode_set``
> +
> +* librte_table: The “key_mask” parameter will be added to all the hash
> tables
> + that currently do not have it, as well as to the hash compute function
> + prototype. The non-“do-sig” versions of the hash tables will be removed
> + (including the “signature_offset” parameter) and the “do-sig” versions
> renamed
> + accordingly.
> --
> 2.7.4
Acked-by: Reshma Pattan <reshma.pattan@intel.com>
next prev parent reply other threads:[~2017-05-09 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 18:22 Cristian Dumitrescu
2017-05-08 8:23 ` Singh, Jasvinder
2017-05-09 16:34 ` Pattan, Reshma [this message]
2017-05-09 16:45 ` Mcnamara, John
2017-05-11 1: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=3AEA2BF9852C6F48A459DA490692831F01139734@irsmsx110.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
/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).