From: Andrew Lunn <andrew@lunn.ch>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
nikolay@cumulusnetworks.com, f.fainelli@gmail.com,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH net-next v2] bridge: fdb add and delete tracepoints
Date: Tue, 29 Aug 2017 15:36:48 +0200 [thread overview]
Message-ID: <20170829133648.GF22093@lunn.ch> (raw)
In-Reply-To: <1503980568-35240-1-git-send-email-roopa@cumulusnetworks.com>
On Mon, Aug 28, 2017 at 09:22:48PM -0700, Roopa Prabhu wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> A few useful tracepoints to trace bridge forwarding
> database updates.
Hi Roopa
Once accepted, it would be nice to add mdb tracepoints as well. I
expect the implementation would be very similar.
Andrew
next prev parent reply other threads:[~2017-08-29 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 4:22 [PATCH net-next v2] bridge: fdb add and delete tracepoints Roopa Prabhu
2017-08-29 10:13 ` Nikolay Aleksandrov
2017-08-29 13:36 ` Andrew Lunn [this message]
2017-08-29 13:49 ` Roopa Prabhu
2017-08-29 16:46 ` Florian Fainelli
2017-08-29 17:36 ` Roopa Prabhu
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=20170829133648.GF22093@lunn.ch \
--to=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@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