From: Atzm Watanabe <atzm@stratosphere.co.jp>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: <netdev@vger.kernel.org>, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH iproute2 v2] vxlan: Allow setting destination to unicast address.
Date: Fri, 12 Apr 2013 14:31:34 +0900 [thread overview]
Message-ID: <87ip3smi15.wl%atzm@stratosphere.co.jp> (raw)
In-Reply-To: <1365702500.7355.0.camel@bwh-desktop.uk.solarflarecom.com>
At Thu, 11 Apr 2013 18:48:20 +0100,
Ben Hutchings wrote:
>
> On Thu, 2013-04-11 at 19:17 +0900, Atzm Watanabe wrote:
> > This patch allows setting VXLAN destination to unicast address.
> > It allows that VXLAN can be used as peer-to-peer tunnel without
> > multicast.
> >
> > v2: use a new argument "remote" instead of "group" based by
> > Stephen Hemminger's comments.
> >
> > Signed-off-by: Atzm Watanabe <atzm@stratosphere.co.jp>
> [...]
> > --- a/ip/iplink_vxlan.c
> > +++ b/ip/iplink_vxlan.c
> > @@ -23,7 +23,8 @@
> >
> > static void explain(void)
> > {
> > - fprintf(stderr, "Usage: ... vxlan id VNI [ group ADDR ] [ local ADDR ]\n");
> > + fprintf(stderr, "Usage: ... vxlan id VNI [ group ADDR ] [ remote ADDR ]\n");
> [...]
>
> Shouldn't that be "[ group|remote ADDR ]", to show that you can specify
> one or the other?
Yes, basically I agreed.
I think this should be "[ { group | remote } ADDR ]",
to accommodate the notation to others.
I'll fix this and resend the patch.
Thanks.
prev parent reply other threads:[~2013-04-12 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 10:17 [PATCH iproute2 v2] vxlan: Allow setting destination to unicast address Atzm Watanabe
2013-04-11 15:24 ` Stephen Hemminger
2013-04-11 17:30 ` David Miller
2013-04-12 5:31 ` Atzm Watanabe
2013-04-11 17:48 ` Ben Hutchings
2013-04-12 5:31 ` Atzm Watanabe [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=87ip3smi15.wl%atzm@stratosphere.co.jp \
--to=atzm@stratosphere.co.jp \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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