From: Phil Yang <Phil.Yang@arm.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dev <dev@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Ruifeng Wang <Ruifeng.Wang@arm.com>,
Joyce Kong <Joyce.Kong@arm.com>, nd <nd@arm.com>,
"thomas@monjalon.net" <thomas@monjalon.net>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] remove RTE CIO barriers
Date: Wed, 23 Sep 2020 09:19:50 +0000 [thread overview]
Message-ID: <DB7PR08MB3865A5C2AC2F2412361DB2B1E9380@DB7PR08MB3865.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8zvVKfE5y_U5AtwYPEzvUdoJEqpLzDxWwa0uoF+yeAuhA@mail.gmail.com>
David Marchand <david.marchand@redhat.com> writes:
> Subject: Re: [dpdk-dev] [PATCH v2 0/2] remove RTE CIO barriers
>
> On Thu, Sep 17, 2020 at 4:23 AM Phil Yang <Phil.Yang@arm.com> wrote:
> > > If there will a v3, can it be possible to have it after next-net pulled
> > > to main repo? Which I am hopping one for this week but need to sync
> with
> > > Thomas. This way no new code is missed.
> >
> > No problem. I will upstream the update after the next-net get merged in
> main repo.
>
> All planets are aligned:
> $ git grep rte_cio next-net/for-main-repo |wc -l
> 81
> $ git grep rte_cio next-net/main |wc -l
> 81
> $ git grep rte_cio origin/main |wc -l
> 81
>
> Can you send a new revision?
> Thanks.
Done. Thanks for your kindly reminder.
Thanks,
Phil
next prev parent reply other threads:[~2020-09-23 9:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 8:40 [dpdk-dev] [PATCH 1/2] drivers: replace RTE CIO barriers with RTE IO barriers Phil Yang
2020-08-24 8:40 ` [dpdk-dev] [PATCH 2/2] eal: remove RTE CIO barriers Phil Yang
2020-08-24 19:38 ` [dpdk-dev] [PATCH 1/2] drivers: replace RTE CIO barriers with RTE IO barriers Honnappa Nagarahalli
2020-08-25 9:08 ` Phil Yang
2020-09-11 5:26 ` [dpdk-dev] [PATCH v2 0/2] remove RTE CIO barriers Phil Yang
2020-09-11 5:26 ` [dpdk-dev] [PATCH v2 1/2] drivers: replace RTE CIO barriers with RTE IO barriers Phil Yang
2020-09-14 23:00 ` Honnappa Nagarahalli
2020-09-11 5:26 ` [dpdk-dev] [PATCH v2 2/2] eal: remove RTE CIO barriers Phil Yang
2020-09-14 22:51 ` Honnappa Nagarahalli
2020-09-16 16:13 ` [dpdk-dev] [PATCH v2 0/2] " David Marchand
2020-09-16 23:22 ` Ferruh Yigit
2020-09-17 2:23 ` Phil Yang
2020-09-23 8:35 ` David Marchand
2020-09-23 9:19 ` Phil Yang [this message]
2020-09-23 9:16 ` [dpdk-dev] [PATCH v3] " Phil Yang
2020-09-23 9:16 ` [dpdk-dev] [PATCH v3] eal: remove deprecated coherent IO memory barriers Phil Yang
2020-09-23 12:20 ` David Marchand
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=DB7PR08MB3865A5C2AC2F2412361DB2B1E9380@DB7PR08MB3865.eurprd08.prod.outlook.com \
--to=phil.yang@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Joyce.Kong@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 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.