From: Jamal Hadi Salim <jhs@mojatatu.com>
To: David Miller <davem@davemloft.net>, roopa@cumulusnetworks.com
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
wkok@cumulusnetworks.com, sfeldma@cumulusnetworks.com,
shm@cumulusnetworks.com
Subject: Re: [PATCH net-next] bridge: Add bridge ifindex to bridge fdb notify msgs
Date: Mon, 02 Jun 2014 18:18:41 -0400 [thread overview]
Message-ID: <538CF841.9010000@mojatatu.com> (raw)
In-Reply-To: <20140602.135014.17031590643529626.davem@davemloft.net>
On 06/02/14 16:50, David Miller wrote:
>
> Jamal, how did the testing go?
>
Works as advertised.
Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
cheers,
jamal
next prev parent reply other threads:[~2014-06-02 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 5:39 [PATCH net-next] bridge: Add bridge ifindex to bridge fdb notify msgs roopa
2014-05-28 11:24 ` Jamal Hadi Salim
2014-06-02 20:50 ` David Miller
2014-06-02 22:18 ` Jamal Hadi Salim [this message]
2014-06-03 0:59 ` 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=538CF841.9010000@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@cumulusnetworks.com \
--cc=shm@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
--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).