From: Thomas Monjalon <thomas@monjalon.net>
To: "Wang, Yipeng1" <yipeng1.wang@intel.com>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"gentoorion@gmail.com" <gentoorion@gmail.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: fix rte_hash_hash comment for ambiguity
Date: Sat, 04 May 2019 23:32:08 +0200 [thread overview]
Message-ID: <3897516.Qjog6bcR5C@xps> (raw)
Message-ID: <20190504213208.rVCGvZZ9FzdYINchlzzYVeA44LM1LFQkvNP8rLYDxiU@z> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F6085A5@IRSMSX103.ger.corp.intel.com>
> > rte_hash_hash is multi-thread safe but not multi-process safe because of
> > the use of function pointers. Previous document and comment says the other
> > way around. This commit fixes the issue.
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-05-04 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 9:40 Yipeng Wang
2019-04-29 9:40 ` Yipeng Wang
2019-04-29 20:05 ` Dharmik Thakkar
2019-04-29 20:05 ` Dharmik Thakkar
2019-04-30 11:20 ` Mcnamara, John
2019-04-30 11:20 ` Mcnamara, John
2019-05-04 21:32 ` Thomas Monjalon [this message]
2019-05-04 21:32 ` 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=3897516.Qjog6bcR5C@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=gentoorion@gmail.com \
--cc=john.mcnamara@intel.com \
--cc=pablo.de.lara.guarch@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 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).