From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev <dev@dpdk.org>,
chas3@att.com, "Zhaohui (zhaohui,
Polestar)" <zhaohui8@huawei.com>
Subject: Re: [dpdk-dev] [PATCH 0/5] bonding fixes
Date: Thu, 21 Mar 2019 21:21:55 +0100 [thread overview]
Message-ID: <CAJFAV8z=F7VNn4cDMe1_8kOpv9SUasavY6PD8ayfnRJZUrwRNw@mail.gmail.com> (raw)
Message-ID: <20190321202155.T-Hfkw-etYAGrIP90cFKzY16l-OqggBDqVk7UPngzuA@z> (raw)
In-Reply-To: <c3f42df5-3973-d24f-e036-05c386ffd879@intel.com>
On Thu, Mar 21, 2019 at 9:12 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 3/20/2019 11:47 AM, David Marchand wrote:
> > Here is a first series of fixes on the bonding driver I caught while
> > reviewing its code.
> >
>
> For series,
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Series applied to dpdk-next-net/master, thanks.
>
Thanks Ferruh.
2 follow up patches from Zhaohui incoming (I was not quick enough).
--
David Marchand
next prev parent reply other threads:[~2019-03-21 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 11:47 David Marchand
2019-03-20 11:47 ` David Marchand
2019-03-20 11:47 ` [dpdk-dev] [PATCH 1/5] doc: fix incorrect bond examples David Marchand
2019-03-20 11:47 ` David Marchand
2019-03-20 11:47 ` [dpdk-dev] [PATCH 2/5] net/bonding: fix incorrect bond port id types David Marchand
2019-03-20 11:47 ` David Marchand
2019-03-20 11:47 ` [dpdk-dev] [PATCH 3/5] net/bonding: fix incorrect slave " David Marchand
2019-03-20 11:47 ` David Marchand
2019-03-20 11:47 ` [dpdk-dev] [PATCH 4/5] net/bonding: fix incorrect packet count type for lacp David Marchand
2019-03-20 11:47 ` David Marchand
2019-03-20 11:47 ` [dpdk-dev] [PATCH 5/5] net/bonding: fix incorrect rxq/txq index types David Marchand
2019-03-20 11:47 ` David Marchand
2019-03-21 20:12 ` [dpdk-dev] [PATCH 0/5] bonding fixes Ferruh Yigit
2019-03-21 20:12 ` Ferruh Yigit
2019-03-21 20:21 ` David Marchand [this message]
2019-03-21 20:21 ` 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='CAJFAV8z=F7VNn4cDMe1_8kOpv9SUasavY6PD8ayfnRJZUrwRNw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=zhaohui8@huawei.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).