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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEP_g=-mSN8zQPv+WjLVZGoQe=_kbU6GkyZ3+nHVfzXMtpXmMQ@mail.gmail.com>
Date:	Fri, 18 Sep 2015 13:14:02 -0700
From:	Jesse Gross <jesse@...ira.com>
To:	"John W. Linville" <linville@...driver.com>
Cc:	netdev <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	Pravin B Shelar <pshelar@...ira.com>,
	Eric Dumazet <eric.dumazet@...il.com>,
	Stephen Hemminger <stephen@...workplumber.org>
Subject: Re: [PATCH] geneve: use network byte order for destination port
 config parameter

On Fri, Sep 18, 2015 at 12:59 PM, John W. Linville
<linville@...driver.com> wrote:
> 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.

Reviewed-by: Jesse Gross <jesse@...ira.com>

Thanks!
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ