From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: mike.rapoport@ravellosystems.com, netdev@vger.kernel.org,
dlstevens@us.ibm.com, tgraf@suug.ch, xiyou.wangcong@gmail.com
Subject: Re: [PATCH net-next v5 5/6] rtnetlink: allow using zero MAC address in rtnl_fdb_{add,del}
Date: Tue, 25 Jun 2013 16:48:32 -0700 (PDT) [thread overview]
Message-ID: <20130625.164832.2025516831400787366.davem@davemloft.net> (raw)
In-Reply-To: <20130625093738.2b3e3a0b@nehalam.linuxnetplumber.net>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 25 Jun 2013 09:37:38 -0700
> This is needed, to avoid breaking bridge use of fdb.
> I will just add it after Mike's patches.
Ok, then I expect this series via a pull request from you Stephen.
Thanks.
next prev parent reply other threads:[~2013-06-25 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 13:01 [PATCH net-next v5 0/6] vxlan: allow specifying multiple default destinations Mike Rapoport
2013-06-25 13:01 ` [PATCH net-next v5 1/6] vxlan: add implicit fdb entry for default destination Mike Rapoport
2013-06-25 13:01 ` [PATCH net-next v5 2/6] vxlan: introduce vxlan_fdb_find_rdst Mike Rapoport
2013-06-25 13:01 ` [PATCH net-next v5 3/6] vxlan: introduce vxlan_fdb_parse Mike Rapoport
2013-06-25 13:01 ` [PATCH net-next v5 4/6] vxlan: allow removal of single destination from fdb entry Mike Rapoport
2013-06-25 13:01 ` [PATCH net-next v5 5/6] rtnetlink: allow using zero MAC address in rtnl_fdb_{add,del} Mike Rapoport
2013-06-25 16:37 ` Stephen Hemminger
2013-06-25 23:48 ` David Miller [this message]
2013-06-25 13:01 ` [PATCH net-next v5 6/6] vxlan: fdb: allow specifying multiple destinations for zero MAC Mike Rapoport
2013-06-25 21:19 ` [PATCH net-next v5 0/6] vxlan: allow specifying multiple default destinations Stephen Hemminger
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=20130625.164832.2025516831400787366.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=mike.rapoport@ravellosystems.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tgraf@suug.ch \
--cc=xiyou.wangcong@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).