From: Thomas Monjalon <thomas@monjalon.net>
To: "Amber, Kumar" <kumar.amber@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Wang, Yipeng1" <yipeng1.wang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] hash: added a new API to hash to query key id
Date: Mon, 20 Jan 2020 01:16:47 +0100 [thread overview]
Message-ID: <6582220.dE46n4Xy2H@xps> (raw)
In-Reply-To: <D2C4A16CA39F7F4E8E384D204491D7A673F3FDB6@ORSMSX104.amr.corp.intel.com>
27/11/2019 02:59, Wang, Yipeng1:
> From: Amber, Kumar
> >Adding new API function to query the maximum key ID
> >that could possibly be returned by rte_hash_add_key and
> >rte_hash_add_key_with_hash. When RTE_HASH_EXTRA_FLAGS_MULTI_WRITER_ADD
> >is set, the maximum key id is larger than the entry count specified
> >by the user.
> >
> >Signed-off-by: Kumar Amber <kumar.amber@intel.com>
> >---
> >+ * - A value indicating the max key of Id key slots present in the table.
> >+ */
> [Wang, Yipeng] typo: key of id -> key Id of
>
> Other than this:
> Acked-by: Yipeng Wang <yipeng1.wang@intel.com>
Applied with typo fixed, thanks
prev parent reply other threads:[~2020-01-20 0:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 14:59 [dpdk-dev] [PATCH v2] hash: added a new API to hash to query key id Kumar Amber
2019-11-22 18:21 ` [dpdk-dev] [PATCH v3] " Kumar Amber
2019-11-25 11:08 ` Kumar Amber
2019-11-25 15:50 ` Amber, Kumar
2019-11-25 16:01 ` Aaron Conole
2019-11-25 16:58 ` Aaron Conole
2019-11-25 17:16 ` Van Haaren, Harry
2019-11-25 17:54 ` Thomas Monjalon
2019-11-25 18:10 ` Aaron Conole
2019-11-25 22:53 ` Aaron Conole
2019-11-26 13:19 ` Van Haaren, Harry
2019-11-26 13:29 ` Van Haaren, Harry
2019-11-26 13:57 ` Aaron Conole
2019-11-27 11:37 ` Van Haaren, Harry
2019-11-26 15:58 ` Aaron Conole
2019-11-25 19:41 ` Wang, Yipeng1
2019-11-26 2:39 ` [dpdk-dev] [PATCH v4] " Kumar Amber
2019-11-27 1:59 ` Wang, Yipeng1
2020-01-20 0:16 ` Thomas Monjalon [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=6582220.dE46n4Xy2H@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=kumar.amber@intel.com \
--cc=yipeng1.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.