From: Jiri Pirko <jiri@resnulli.us>
To: Ivan Vecera <cera@cera.cz>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
davem@davemloft.net, bridge@lists.linux-foundation.org,
jiri@mellanox.com
Subject: Re: [PATCH net v2] bridge: netlink: call br_changelink() during br_dev_newlink()
Date: Fri, 20 Jan 2017 18:08:47 +0100 [thread overview]
Message-ID: <20170120170847.GA1784@nanopsycho.orion> (raw)
In-Reply-To: <20170120165933.19991-1-cera@cera.cz>
Fri, Jan 20, 2017 at 05:59:33PM CET, cera@cera.cz wrote:
>Any bridge options specified during link creation (e.g. ip link add)
>are ignored as br_dev_newlink() does not process them.
>Use br_changelink() to do it.
>
>Fixes: 1332351 bridge: implement rtnl_link_ops->changelink
This is not the correct "Fixes" format.
prev parent reply other threads:[~2017-01-20 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 16:59 [PATCH net v2] bridge: netlink: call br_changelink() during br_dev_newlink() Ivan Vecera
2017-01-20 17:08 ` Jiri Pirko [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=20170120170847.GA1784@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=bridge@lists.linux-foundation.org \
--cc=cera@cera.cz \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).