From: David Miller <davem@davemloft.net>
To: linus.luessing@c0d3.blue
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org,
roopa@cumulusnetworks.com, bridge@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, wkok@cumulusnetworks.com,
cwang@twopensource.com
Subject: Re: [Bridge] [PATCHv3 net-next] bridge: allow setting hash_max + multicast_router if interface is down
Date: Mon, 25 May 2015 17:28:18 -0400 (EDT) [thread overview]
Message-ID: <20150525.172818.2000334376621437405.davem@davemloft.net> (raw)
In-Reply-To: <1432343554-3493-1-git-send-email-linus.luessing@c0d3.blue>
From: Linus Lüssing <linus.luessing@c0d3.blue>
Date: Sat, 23 May 2015 03:12:34 +0200
> Network managers like netifd (used in OpenWRT for instance) try to
> configure interface options after creation but before setting the
> interface up.
>
> Unfortunately the sysfs / bridge currently only allows to configure the
> hash_max and multicast_router options when the bridge interface is up.
> But since br_multicast_init() doesn't start any timers and only sets
> default values and initializes timers it should be save to reconfigure
> the default values after that, before things actually get active after
> the bridge is set up.
>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
Applied to net-next, thanks.
prev parent reply other threads:[~2015-05-25 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 1:12 [Bridge] [PATCHv3 net-next] bridge: allow setting hash_max + multicast_router if interface is down Linus Lüssing
2015-05-25 21:28 ` David Miller [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=20150525.172818.2000334376621437405.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=cwang@twopensource.com \
--cc=herbert@gondor.apana.org.au \
--cc=linus.luessing@c0d3.blue \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=wkok@cumulusnetworks.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).