From: Jamal Hadi Salim <jhs@mojatatu•com>
To: David Miller <davem@davemloft•net>
Cc: stephen@networkplumber•org, netdev@vger•kernel.org,
vyasevic@redhat•com, sfeldma@cumulusnetworks•com,
john.r.fastabend@intel•com, roopa@cumulusnetworks•com
Subject: Re: [net-next PATCH 1/2] bridge fdb dumping takes a filter device Dumping a bridge fdb dumps every fdb entry held. With this change we are going to filter on selected bridge port.
Date: Sat, 07 Jun 2014 08:41:00 -0400 [thread overview]
Message-ID: <5393085C.6030405@mojatatu.com> (raw)
In-Reply-To: <20140605.001514.517987695784091540.davem@davemloft.net>
On 06/05/14 03:15, David Miller wrote:
>
> Jamal take it easy with the subject lines :-)
>
LOL.Cant think of anything clever to say to that.
Maybe you should just accept my attachments ;->
Anyways, I have to resend the patches to consider
the comments from Vlad.
cheers,
jamal
prev parent reply other threads:[~2014-06-07 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 11:56 [net-next PATCH 1/2] bridge fdb dumping takes a filter device Dumping a bridge fdb dumps every fdb entry held. With this change we are going to filter on selected bridge port Jamal Hadi Salim
2014-06-01 11:56 ` [net-next PATCH 2/2] bridge netlink dump interface at par with brctl Actually better than brctl showmacs because we can filter by bridge port in the kernel Jamal Hadi Salim
2014-06-01 12:16 ` Jamal Hadi Salim
2014-06-01 12:24 ` Jamal Hadi Salim
2014-06-02 15:34 ` Vlad Yasevich
2014-06-02 22:17 ` Jamal Hadi Salim
2014-06-05 7:15 ` [net-next PATCH 1/2] bridge fdb dumping takes a filter device Dumping a bridge fdb dumps every fdb entry held. With this change we are going to filter on selected bridge port David Miller
2014-06-07 12:41 ` Jamal Hadi Salim [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=5393085C.6030405@mojatatu.com \
--to=jhs@mojatatu$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=john.r.fastabend@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=roopa@cumulusnetworks$(echo .)com \
--cc=sfeldma@cumulusnetworks$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=vyasevic@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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