From: Thomas Monjalon <thomas@monjalon.net>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: dev@dpdk.org, "De Lara Guarch,
Pablo" <pablo.de.lara.guarch@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] lib/librte_hash: fix incorrect comment for lookup
Date: Sun, 15 Apr 2018 15:08:28 +0200 [thread overview]
Message-ID: <1562016.b1YM9cIy2D@xps> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CCD1B9A@IRSMSX108.ger.corp.intel.com>
> > rte_hash_lookup_with_hash() has wrong comment for its 'sig' param.
> >
> > Fixes: 1a9f648be291 ("hash: fix for multi-process apps")
> >
> > Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
> Also, this should be backported to the stable branch, so I CC stable@dpdk.org.
Applied, thanks
prev parent reply other threads:[~2018-04-15 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 12:33 Shreyansh Jain
2018-04-12 14:27 ` De Lara Guarch, Pablo
2018-04-15 13:08 ` 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=1562016.b1YM9cIy2D@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=stable@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).