From: David Miller <davem@davemloft.net>
To: jhs@mojatatu.com
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
vyasevic@redhat.com, sfeldma@cumulusnetworks.com,
john.r.fastabend@intel.com, roopa@cumulusnetworks.com,
eric.dumazet@gmail.com
Subject: Re: [net-next-2.6 PATCH v5 0/2] bridge: fdb dumping takes a filter device
Date: Tue, 08 Jul 2014 14:10:38 -0700 (PDT) [thread overview]
Message-ID: <20140708.141038.712786607116212110.davem@davemloft.net> (raw)
In-Reply-To: <1404380290-17040-1-git-send-email-jhs@emojatatu.com>
From: Jamal Hadi Salim <jhs@mojatatu.com>
Date: Thu, 3 Jul 2014 05:38:08 -0400
> Changes:
> v5:
> Embarassing qlnic compile failure found by DaveM
>
> v4:
> Request from DaveM to use proper comment tagging and remove if-stmnt braces
>
> V3:
> Suggestion from Eric D. to use for_each_netdev
> Suggestion from Stephen H. to reduce level of indentation
>
> V2:
> Suggestions from Vlad
> Get rid of rcu read lock since rtnl_lock is being held
> simplify for readability
Series applied, I'll push it out after doing another build test :-)
next prev parent reply other threads:[~2014-07-08 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 9:38 [net-next-2.6 PATCH v5 0/2] bridge: fdb dumping takes a filter device Jamal Hadi Salim
2014-07-03 9:38 ` [net-next-2.6 PATCH v5 1/2] " Jamal Hadi Salim
2014-07-03 12:23 ` Varka Bhadram
2014-07-03 9:38 ` [net-next-2.6 PATCH v5 2/2] bridge: netlink dump interface at par with brctl Jamal Hadi Salim
2014-07-03 12:24 ` Varka Bhadram
2014-07-08 21:10 ` David Miller [this message]
2014-07-08 21:21 ` [net-next-2.6 PATCH v5 0/2] bridge: fdb dumping takes a filter device David Miller
2014-07-10 10:23 ` Jamal Hadi Salim
2014-07-10 19:20 ` 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=20140708.141038.712786607116212110.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
--cc=vyasevic@redhat.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).