From: David Marchand <david.marchand@redhat.com>
To: Chas Williams <3chas3@gmail.com>
Cc: dev <dev@dpdk.org>, "Yigit, Ferruh" <ferruh.yigit@intel.com>,
chas3@att.com, "Zhaohui (zhaohui,
Polestar)" <zhaohui8@huawei.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 1/2] net/bonding: fix more incorrect slave id types
Date: Sun, 24 Mar 2019 18:13:17 +0100 [thread overview]
Message-ID: <CAJFAV8wCFJipWHDmGR2gM9ieLCvzyeryztffQEjF1mihiAXRmQ@mail.gmail.com> (raw)
In-Reply-To: <8001e759-dfc7-28f7-3a14-80d6af8943a5@gmail.com>
On Sun, Mar 24, 2019 at 2:28 PM Chas Williams <3chas3@gmail.com> wrote:
> See inline.
>
> On 3/21/19 4:28 PM, David Marchand wrote:
> > From: Zhaohui <zhaohui8@huawei.com>
> >
> > mode_bond_id and mode_band_id are slave ids, stored on 16bits.
>
> Please change mode_bond_id to mode_count_id in this commit message.
> Otherwise, this looks fine.
>
Indeed... I should have gone to bed earlier ;-)
--
David Marchand
prev parent reply other threads:[~2019-03-24 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 20:28 [dpdk-stable] " David Marchand
2019-03-21 20:28 ` [dpdk-stable] [PATCH 2/2] net/bonding: fix oob access in "other" aggregator modes David Marchand
2019-03-22 11:18 ` [dpdk-stable] [dpdk-dev] " Maxime Coquelin
2019-03-24 13:35 ` Chas Williams
2019-03-24 17:11 ` David Marchand
2019-03-24 17:24 ` Chas Williams
2019-03-24 18:01 ` David Marchand
2019-09-30 13:49 ` Yigit, Ferruh
2019-03-22 11:18 ` [dpdk-stable] [dpdk-dev] [PATCH 1/2] net/bonding: fix more incorrect slave id types Maxime Coquelin
2019-09-30 13:49 ` Yigit, Ferruh
2019-03-24 13:28 ` Chas Williams
2019-03-24 17:13 ` 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=CAJFAV8wCFJipWHDmGR2gM9ieLCvzyeryztffQEjF1mihiAXRmQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
--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).