From: Stephen Hemminger <stephen@networkplumber.org>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, Phil Sutter <phil@nwl.cc>,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
David Ahern <dsa@cumulusnetworks.com>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: [PATCH iproute2] ip: Use specific slave id
Date: Thu, 22 Sep 2016 16:40:47 -0700 [thread overview]
Message-ID: <20160922164047.1180acad@xeon-e3> (raw)
In-Reply-To: <1474365732-6087-1-git-send-email-liuhangbin@gmail.com>
On Tue, 20 Sep 2016 18:02:12 +0800
Hangbin Liu <liuhangbin@gmail.com> wrote:
> The original bond/bridge/vrf and slaves use same id, which make people
> confused. Use bond/bridge/vrf_slave as id name will make code more clear.
>
> Acked-by: Phil Sutter <psutter@redhat.com>
> Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
> ---
Applied
prev parent reply other threads:[~2016-09-22 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 10:02 [PATCH iproute2] ip: Use specific slave id Hangbin Liu
2016-09-22 23:40 ` Stephen Hemminger [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=20160922164047.1180acad@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dsa@cumulusnetworks.com \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=phil@nwl.cc \
--cc=sd@queasysnail.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).