netdev - Re: [PATCH v2] geneve: use network byte order for destination port config parameter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20150923.154136.1784019012935564685.davem@davemloft.net>
Date:	Wed, 23 Sep 2015 15:41:36 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	linville@...driver.com
Cc:	netdev@...r.kernel.org, pshelar@...ira.com, jesse@...ira.com,
	eric.dumazet@...il.com, stephen@...workplumber.org
Subject: Re: [PATCH v2] geneve: use network byte order for destination port
 config parameter

From: "John W. Linville" <linville@...driver.com>
Date: Tue, 22 Sep 2015 13:09:32 -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@...driver.com>
> ---
> It is OK to change this, since this parameter was introduced to
> net-next in the pre-4.3 cycle.  Using network byte order for this
> parameter is consistent with what the other tunnels are doing.
> 
> v2 -- rebase on current net tree...

Applied, thanks John.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html