From: Stephen Hemminger <stephen@networkplumber.org>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next iproute2] support batching of ip route get commands
Date: Mon, 20 Jul 2015 14:56:09 -0700 [thread overview]
Message-ID: <20150720145609.77a0d85c@urahara> (raw)
In-Reply-To: <1437005196-8914-1-git-send-email-roopa@cumulusnetworks.com>
On Wed, 15 Jul 2015 17:06:36 -0700
Roopa Prabhu <roopa@cumulusnetworks.com> wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This patch replaces exits with returns in
> ip route get command handling. This allows batching
> of ip route get commands.
>
> $cat route_get_batch.txt
> route get 10.0.14.2
> route get 12.0.14.2
> route get 10.0.14.4
>
> $ip -batch route_get_batch.txt
> local 10.0.14.2 dev lo src 10.0.14.2
> cache <local>
> 12.0.14.2 via 192.168.0.2 dev eth0 src 192.168.0.15
> cache
> 10.0.14.4 dev dummy0 src 10.0.14.2
> cache
>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Looks good and simple, applied.
prev parent reply other threads:[~2015-07-20 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 0:06 [PATCH net-next iproute2] support batching of ip route get commands Roopa Prabhu
2015-07-20 21:56 ` Stephen Hemminger [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=20150720145609.77a0d85c@urahara \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@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).