From: David Marchand <david.marchand@redhat.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Jerin Jacob" <jerinjacobk@gmail.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Olivier Matz" <olivier.matz@6wind.com>,
"David Christensen" <drc@linux.vnet.ibm.com>,
"Stephen Hemminger" <stephen@networkplumber.org>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [RFC] ring: make ring implementation non-inlined
Date: Wed, 1 Jul 2020 16:31:18 +0200 [thread overview]
Message-ID: <CAJFAV8yS63C9LsjZuN7g8_1Hn0Xde08dBkF+Zo2WyHWu9R2C9A@mail.gmail.com> (raw)
In-Reply-To: <AM4PR0802MB22127348FE4C25CF96B49112986C0@AM4PR0802MB2212.eurprd08.prod.outlook.com>
On Wed, Jul 1, 2020 at 4:11 PM Honnappa Nagarahalli
<Honnappa.Nagarahalli@arm.com> wrote:
> > Yes, please reject it.
> I just tried to mark it rejected in patchwork, I do not have the permissions (probably you are the owner of the patch). Can you please mark it?
Indeed, Konstantin should be able to do it.
I just flagged it Rejected.
There are still some ring patches waiting in pw, could you and
Konstantin agree on/flag them?
Thanks.
--
David Marchand
prev parent reply other threads:[~2020-07-01 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 16:41 Konstantin Ananyev
2020-03-20 17:54 ` Stephen Hemminger
2020-03-21 1:03 ` Ananyev, Konstantin
2020-03-25 21:09 ` Jerin Jacob
2020-03-26 0:28 ` Ananyev, Konstantin
2020-03-26 8:04 ` Morten Brørup
2020-03-31 23:25 ` Thomas Monjalon
2020-06-30 23:15 ` Honnappa Nagarahalli
2020-07-01 7:27 ` Morten Brørup
2020-07-01 12:21 ` Ananyev, Konstantin
2020-07-01 14:11 ` Honnappa Nagarahalli
2020-07-01 14:31 ` David Marchand [this message]
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=CAJFAV8yS63C9LsjZuN7g8_1Hn0Xde08dBkF+Zo2WyHWu9R2C9A@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=konstantin.ananyev@intel.com \
--cc=mb@smartsharesystems.com \
--cc=nd@arm.com \
--cc=olivier.matz@6wind.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).