From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"David Marchand" <david.marchand@redhat.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 21/01/2021
Date: Fri, 22 Jan 2021 12:11:08 +0000 [thread overview]
Message-ID: <BYAPR11MB3301DE274BC16F618ECF55E89AA09@BYAPR11MB3301.namprd11.prod.outlook.com> (raw)
In-Reply-To: <VI1PR0802MB2351C63350F26C9BECAFAB7A9EA00@VI1PR0802MB2351.eurprd08.prod.outlook.com>
> > * Is ring library refactoring work stalled? Arm will check.
> > * https://patches.dpdk.org/project/dpdk/list/?series=14405
>
> IMO, this series is in good shape.
> There is no comments from community on this series.
> But this work is based on discussion between ring library maintainers (Honnappa, Konstantin):
> https://mails.dpdk.org/archives/dev/2020-May/166803.html
> Honnappa has already reviewed this series. It will be good if Konstantin can also review and add a tag.
Sorry, missed it somehow.
Will have a look later today.
> So I think this series can be queued for merge.
>
> PS: The ring test comment mentioned in the meeting is about another patch series:
> http://patches.dpdk.org/patch/85641/
>
next prev parent reply other threads:[~2021-01-22 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 12:04 Ferruh Yigit
2021-01-22 6:38 ` Ruifeng Wang
2021-01-22 12:11 ` Ananyev, Konstantin [this message]
2021-01-26 9:04 ` Ferruh Yigit
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=BYAPR11MB3301DE274BC16F618ECF55E89AA09@BYAPR11MB3301.namprd11.prod.outlook.com \
--to=konstantin.ananyev@intel.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=nd@arm.com \
--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).