netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsa@cumulusnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, shm@cumulusnetworks.com,
	roopa@cumulusnetworks.com
Subject: Re: [PATCH net-next v3] net: Add fib rules at vrf device create
Date: Wed, 9 Dec 2015 16:04:53 -0700	[thread overview]
Message-ID: <5668B395.2030604@cumulusnetworks.com> (raw)
In-Reply-To: <20151209.172207.663308411545854156.davem@davemloft.net>

On 12/9/15 3:22 PM, David Miller wrote:
> Just write a script already...

Why do you think this took so long to bubble up?

I wrote a script back in July -- well before VRF was accepted into your 
tree -- that I use for testing. This request comes from other users 
starting to work with VRFs.

      reply	other threads:[~2015-12-09 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 17:43 [PATCH net-next v3] net: Add fib rules at vrf device create David Ahern
2015-12-09 20:13 ` David Miller
2015-12-09 22:05   ` David Ahern
2015-12-09 22:22     ` David Miller
2015-12-09 23:04       ` David Ahern [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=5668B395.2030604@cumulusnetworks.com \
    --to=dsa@cumulusnetworks.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=shm@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).