From: Thomas Monjalon <thomas@monjalon.net>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
Phil Yang <Phil.Yang@arm.com>
Cc: "konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Ruifeng Wang <Ruifeng.Wang@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] remove mbuf deprecated filed
Date: Mon, 14 Sep 2020 10:47:31 +0200 [thread overview]
Message-ID: <3073227.ZvxGrIcxYx@thomas> (raw)
In-Reply-To: <DB7PR08MB38653C5A8D06A46958A1D707E9240@DB7PR08MB3865.eurprd08.prod.outlook.com>
11/09/2020 12:57, Phil Yang:
> Andrew Rybchenko <arybchenko@solarflare.com> writes:
>
> <snip>
> > On 9/11/20 10:35 AM, Phil Yang wrote:
> > > Remove the deprecated[1] refcnt_atomic member in structures rte_mbuf
> > and
> > > rte_mbuf_ext_shared_info.
> > >
> > > [1]
> > http://code.dpdk.org/dpdk/latest/source/doc/guides/rel_notes/deprecatio
> > n.rst#L161
> >
> > LGTM, please, cleanup deprecation notice in this patches when
> > corresponding changes are done.
>
> OK. Will do.
I will do it while squashing and merging the patches.
next prev parent reply other threads:[~2020-09-14 8:47 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 [this message]
2020-09-14 12:25 ` [dpdk-dev] [PATCH v3] mbuf: remove atomic reference counters Thomas Monjalon
2020-09-14 12:35 ` Thomas Monjalon
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=3073227.ZvxGrIcxYx@thomas \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Phil.Yang@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=olivier.matz@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.