DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Phil Yang <phil.yang@arm.com>, arybchenko@solarflare.com
Cc: dev@dpdk.org, konstantin.ananyev@intel.com,
	david.marchand@redhat.com, honnappa.nagarahalli@arm.com,
	nd@arm.com, Ruifeng wang <ruifeng.wang@arm.com>,
	Ray Kinsella <mdr@ashroe.eu>, Neil Horman <nhorman@tuxdriver.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v3] mbuf: remove atomic reference counters
Date: Mon, 14 Sep 2020 14:35:19 +0200	[thread overview]
Message-ID: <2541212.lAx71QvhzZ@thomas> (raw)
In-Reply-To: <20200914122557.95278-1-thomas@monjalon.net>

I wrote:
> From: Phil Yang <phil.yang@arm.com>
> 
> Remove the deprecated refcnt_atomic union fields in
> rte_mbuf and rte_mbuf_ext_shared_info structures.
> 
> Signed-off-by: Phil Yang <phil.yang@arm.com>
> Reviewed-by: Ruifeng wang <ruifeng.wang@arm.com>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> 
> v2:
>     - squashed
>     - removed deprecation notice
>     - updated release notes (in API section)
> 
> v3:
>     - re-sent with --in-reply-to
>     - added Andrew's ack

The ack is missing above,
Anyway, applied with the ack :)



  reply	other threads:[~2020-09-14 12:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11  7:35 [dpdk-dev] [PATCH 0/2] remove mbuf deprecated filed Phil Yang
2020-09-11  7:35 ` [dpdk-dev] [PATCH 1/2] mbuf: remove generic mbuf atomically accessed refcnt Phil Yang
2020-09-11  7:35 ` [dpdk-dev] [PATCH 2/2] mbuf: remove external buffer " Phil Yang
2020-09-11  7:39 ` [dpdk-dev] [PATCH 0/2] remove mbuf deprecated filed Andrew Rybchenko
2020-09-11 10:57   ` Phil Yang
2020-09-14  8:47     ` Thomas Monjalon
2020-09-14 12:25 ` [dpdk-dev] [PATCH v3] mbuf: remove atomic reference counters Thomas Monjalon
2020-09-14 12:35   ` Thomas Monjalon [this message]
2020-09-14 13:48     ` Phil Yang

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=2541212.lAx71QvhzZ@thomas \
    --to=thomas@monjalon.net \
    --cc=arybchenko@solarflare.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=john.mcnamara@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=mdr@ashroe.eu \
    --cc=nd@arm.com \
    --cc=nhorman@tuxdriver.com \
    --cc=olivier.matz@6wind.com \
    --cc=phil.yang@arm.com \
    --cc=ruifeng.wang@arm.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).