From: Stephen Hemminger <stephen@networkplumber.org>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, joerg@higgsboson.tk, davem@davemloft.net
Subject: Re: [PATCH iproute2 net-next 0/3] iplink_bridge: add support for ageing_time, priority and stp_state
Date: Fri, 26 Jun 2015 00:07:42 -0400 [thread overview]
Message-ID: <20150626000742.105a5908@uryu.home.lan> (raw)
In-Reply-To: <1434451129-3241-1-git-send-email-razor@blackwall.org>
On Tue, 16 Jun 2015 13:38:46 +0300
Nikolay Aleksandrov <razor@blackwall.org> wrote:
> Hi,
> Three months ago support was added to be able to set ageing_time,
> priority and stp_state via netlink by commit:
> af615762e972 ("bridge: add ageing_time, stp_state, priority over netlink")
> This patch-set adds support for iproute2 to be able to use them.
> Exampes:
> ip link set dev br0 type bridge priority 10
> ip link set dev br0 type bridge ageing_time 10
> ip link set dev br0 type bridge stp_state 1
>
>
> Best regards,
> Nikolay Aleksandrov
>
> Nikolay Aleksandrov (3):
> iplink_bridge: add support for ageing_time
> iplink_bridge: add support for stp_state
> iplink_bridge: add support for priority
>
> ip/iplink_bridge.c | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
All these are staged in net-next branch.
prev parent reply other threads:[~2015-06-26 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 10:38 [PATCH iproute2 net-next 0/3] iplink_bridge: add support for ageing_time, priority and stp_state Nikolay Aleksandrov
2015-06-16 10:38 ` [PATCH iproute2 net-next 1/3] iplink_bridge: add support for ageing_time Nikolay Aleksandrov
2015-06-16 10:38 ` [PATCH iproute2 net-next 2/3] iplink_bridge: add support for stp_state Nikolay Aleksandrov
2015-06-16 10:38 ` [PATCH iproute2 net-next 3/3] iplink_bridge: add support for priority Nikolay Aleksandrov
2015-06-26 4:07 ` 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=20150626000742.105a5908@uryu.home.lan \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=joerg@higgsboson.tk \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
/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).