From: David Miller <davem@davemloft.net>
To: sfeldma@gmail.com
Cc: roopa@cumulusnetworks.com, siva.mannem.lnx@gmail.com,
netdev@vger.kernel.org, sfeldma@cumulusnetworks.com,
jiri@resnulli.us
Subject: Re: [PATCH net-next] bridge: Let bridge not age 'externally' learnt FDB entries, they are removed when 'external' entity notifies the aging
Date: Wed, 04 Feb 2015 23:53:08 -0800 (PST) [thread overview]
Message-ID: <20150204.235308.71797582017426266.davem@davemloft.net> (raw)
In-Reply-To: <CAE4R7bCASKHmZD+tiu=ZWM9dzvTrSLsaXxgtOYLpsmOR87kcTQ@mail.gmail.com>
From: Scott Feldman <sfeldma@gmail.com>
Date: Wed, 4 Feb 2015 23:13:07 -0800
> I'd like to see this patch reverted so we can have a more
> comprehensive discussion/solution. With this patch applied, the only
> user (rocker) of NETDEV_SWITCH_FDB_ADD is broken. So please undo this
> patch so rocker isn't broken and let's work on a knob to suit both
> modes: 1) let bridge manage aging, 2) let device manage aging.
Patch reverted.
next prev parent reply other threads:[~2015-02-05 7:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 17:21 [PATCH net-next] bridge: Let bridge not age 'externally' learnt FDB entries, they are removed when 'external' entity notifies the aging Siva Mannem
2015-02-03 15:11 ` roopa
2015-02-04 8:02 ` Siva Mannem
2015-02-04 16:19 ` roopa
2015-02-05 7:13 ` Scott Feldman
2015-02-05 7:53 ` David Miller [this message]
2015-02-05 10:26 ` Siva Mannem
2015-02-05 11:05 ` B Viswanath
2015-02-05 17:10 ` Scott Feldman
2015-02-05 17:55 ` Scott Feldman
2015-02-05 18:31 ` B Viswanath
2015-02-06 1:45 ` Scott Feldman
2015-02-06 3:27 ` Siva Mannem
2015-02-07 5:53 ` Scott Feldman
2015-02-04 21:51 ` David Miller
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=20150204.235308.71797582017426266.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=siva.mannem.lnx@gmail.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).