All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: roopa@cumulusnetworks.com
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
	nolan@cumulusnetworks.com, shm@cumulusnetworks.com,
	wkok@cumulusnetworks.com
Subject: Re: [PATCH v2 net-next] bridge: Add fdb dst check during fdb update
Date: Mon, 22 Apr 2013 16:12:13 -0400 (EDT)	[thread overview]
Message-ID: <20130422.161213.1693081623580531501.davem@davemloft.net> (raw)
In-Reply-To: <1365968593-28725-1-git-send-email-roopa@cumulusnetworks.com>


Ok, if nobody with bridgining expertiece can be bothered to review
this I'm simply not going to apply it, it must not be that important.

  parent reply	other threads:[~2013-04-22 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 19:43 [PATCH v2 net-next] bridge: Add fdb dst check during fdb update roopa
2013-04-19 20:51 ` David Miller
2013-04-22 20:12 ` David Miller [this message]
2013-04-22 22:56 ` [PATCH v3 " Stephen Hemminger
2013-04-29 15:41   ` 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=20130422.161213.1693081623580531501.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=nolan@cumulusnetworks.com \
    --cc=roopa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.