From: Thomas Monjalon <thomas@monjalon.net>
To: pablo.de.lara.guarch@intel.com, john.mcnamara@intel.com,
marko.kovacevic@intel.com
Cc: dev@dpdk.org, Yipeng Wang <yipeng1.wang@intel.com>,
bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] doc: add multithread description to hash library
Date: Sun, 05 Aug 2018 22:29:00 +0200 [thread overview]
Message-ID: <2185246.XqZznXKiCj@xps> (raw)
In-Reply-To: <1532627761-256100-1-git-send-email-yipeng1.wang@intel.com>
Pablo, Marko, review please?
26/07/2018 19:56, Yipeng Wang:
> Added multithreading related description into programmer
> guide of hash library.
>
> Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com>
next prev parent reply other threads:[~2018-08-05 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 17:56 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
2018-08-05 20:29 ` Thomas Monjalon [this message]
2018-08-09 13:00 ` [dpdk-dev] [PATCH 1/2] doc: add multithread description to hash library 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=2185246.XqZznXKiCj@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).