From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Wang, Yipeng1" <yipeng1.wang@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] hash: add more accurate thread-safety comments
Date: Thu, 9 Aug 2018 13:00:39 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F929AA8@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1532627761-256100-2-git-send-email-yipeng1.wang@intel.com>
> -----Original Message-----
> From: Wang, Yipeng1
> Sent: Thursday, July 26, 2018 6:56 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Kovacevic, Marko <marko.kovacevic@intel.com>
> Cc: dev@dpdk.org; Wang, Yipeng1 <yipeng1.wang@intel.com>; Richardson,
> Bruce <bruce.richardson@intel.com>
> Subject: [PATCH 2/2] hash: add more accurate thread-safety comments
>
> Describing the thread-safety support more accurately for API documentation.
>
> Fixes: f2e3001b53ec ("hash: support read/write concurrency")
>
> Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2018-08-09 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 17:56 [dpdk-dev] [PATCH 1/2] doc: add multithread description to hash library Yipeng Wang
2018-07-26 17:56 ` [dpdk-dev] [PATCH 2/2] hash: add more accurate thread-safety comments Yipeng Wang
2018-08-09 13:00 ` De Lara Guarch, Pablo [this message]
2018-08-05 20:29 ` [dpdk-dev] [PATCH 1/2] doc: add multithread description to hash library Thomas Monjalon
2018-08-09 13:00 ` De Lara Guarch, Pablo
2018-08-09 20:00 ` 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=E115CCD9D858EF4F90C690B0DCB4D8977F929AA8@IRSMSX107.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).