From: Thomas Graf <tgraf@suug.ch>
To: roopa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, shemminger@vyatta.com,
vyasevic@redhat.com, john.fastabend@gmail.com, jhs@mojatatu.com,
sfeldma@gmail.com, jiri@resnulli.us, wkok@cumulusnetworks.com
Subject: Re: [PATCH net-next] bridge: fix setlink/dellink notifications
Date: Wed, 14 Jan 2015 19:41:37 +0000 [thread overview]
Message-ID: <20150114194137.GC2105@casper.infradead.org> (raw)
In-Reply-To: <1421218123-18346-1-git-send-email-roopa@cumulusnetworks.com>
On 01/13/15 at 10:48pm, roopa@cumulusnetworks.com wrote:
> 2) Generate one notification from master and the other notification from
> self (This seems to be ideal):
> For master: the master driver will send notification (bridge in this
> example)
> For self: the self driver will send notification (rocker in the above
> example. It can use helpers from rtnetlink.c to do so. Like the
> ndo_dflt_bridge_getlink api).
>
> This patch implements 2) (leaving the 'rtnl_bridge_notify' around to be used
> with 'self').
>
> CC'ing others who might be affected by this change for review.
>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
I haven't digested this line by line yet but I agree that what you
describe above would be a good end state.
If I read the patch correctly then we would omit one notification
for the master case. Were both notifications exactly identical
previously?
This has the chance of breaking existing users terribly.
next prev parent reply other threads:[~2015-01-14 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 6:48 [PATCH net-next] bridge: fix setlink/dellink notifications roopa
2015-01-14 19:41 ` Thomas Graf [this message]
2015-01-14 20:57 ` roopa
2015-01-14 23:22 ` Arad, Ronen
2015-01-14 23:36 ` John Fastabend
2015-01-14 23:56 ` roopa
2015-01-15 0:01 ` tgraf
2015-01-14 23:54 ` roopa
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=20150114194137.GC2105@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=shemminger@vyatta.com \
--cc=vyasevic@redhat.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).