DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Christensen <drc@linux.vnet.ibm.com>
To: Phil Yang <phil.yang@arm.com>, dev@dpdk.org
Cc: bruce.richardson@intel.com, ferruh.yigit@intel.com,
	hemant.agrawal@nxp.com, honnappa.nagarahalli@arm.com,
	jerinj@marvell.com, ktraynor@redhat.com,
	konstantin.ananyev@intel.com, maxime.coquelin@redhat.com,
	olivier.matz@6wind.com, stephen@networkplumber.org,
	thomas@monjalon.net, ruifeng.wang@arm.com, nd@arm.com
Subject: Re: [dpdk-dev] [PATCH] doc: announce adoption of C11 atomic operations semantics
Date: Thu, 21 May 2020 12:34:00 -0700	[thread overview]
Message-ID: <2086d3f3-a0aa-a2c7-d3d3-3e30d720c6db@linux.vnet.ibm.com> (raw)
In-Reply-To: <1588835193-27550-1-git-send-email-phil.yang@arm.com>



On 5/7/20 12:06 AM, Phil Yang wrote:
> From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> 
> As agreed in the DPDK tech board [1], after 20.05 release, patches must
> use C11 atomic operations semantics with the help of wrappers.
> 
> [1] http://mails.dpdk.org/archives/dev/2020-April/165143.html
> 
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Reviewed-by: Phil Yang <phil.yang@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>

Acked-by: David Christensen <drc@linux.vnet.ibm.com>

  parent reply	other threads:[~2020-05-21 19:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  7:06 Phil Yang
2020-05-07 21:00 ` Stephen Hemminger
2020-05-08  3:46   ` Honnappa Nagarahalli
2020-05-21  4:31 ` Honnappa Nagarahalli
2020-05-21  5:04   ` Hemant Agrawal
2020-05-21  4:56 ` Jerin Jacob
2020-05-21 10:33   ` Ananyev, Konstantin
2020-05-21 19:34 ` David Christensen [this message]
2020-05-22  4:30 ` [dpdk-dev] [PATCH v2] " Honnappa Nagarahalli
2020-05-22  8:37   ` Ananyev, Konstantin
2020-05-24 23:54     ` 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=2086d3f3-a0aa-a2c7-d3d3-3e30d720c6db@linux.vnet.ibm.com \
    --to=drc@linux.vnet.ibm.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=nd@arm.com \
    --cc=olivier.matz@6wind.com \
    --cc=phil.yang@arm.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).