From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, pshelar@nicira.com,
eric.dumazet@gmail.com, jesse@nicira.com,
stephen@networkplumber.org
Subject: Re: [PATCH] geneve: use network byte order for destination port config parameter
Date: Tue, 22 Sep 2015 11:25:05 -0400 [thread overview]
Message-ID: <20150922152504.GA18514@tuxdriver.com> (raw)
In-Reply-To: <20150921.162404.1245771010622997220.davem@davemloft.net>
On Mon, Sep 21, 2015 at 04:24:04PM -0700, David Miller wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Fri, 18 Sep 2015 15:59:10 -0400
>
> > This is primarily for consistancy with vxlan and other tunnels which
> > use network byte order for similar parameters.
> >
> > Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
> This doesn't apply to any of my trees. Can you respin it against
> 'net'? Thanks.
Sure -- sorry about that!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2015-09-22 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 19:27 [PATCH] iplink_geneve: add UDP destination port configuration at link creation John W. Linville
2015-09-17 20:49 ` Eric Dumazet
2015-09-18 14:26 ` John W. Linville
2015-09-18 14:45 ` Eric Dumazet
2015-09-18 16:15 ` Jesse Gross
2015-09-18 18:39 ` John W. Linville
2015-09-18 19:59 ` [PATCH] geneve: use network byte order for destination port config parameter John W. Linville
2015-09-18 20:14 ` Jesse Gross
2015-09-21 23:24 ` David Miller
2015-09-22 15:25 ` John W. Linville [this message]
2015-09-22 17:09 ` [PATCH v2] " John W. Linville
2015-09-23 22: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=20150922152504.GA18514@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--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;
as well as URLs for NNTP newsgroup(s).