netdev - Re: [PATCH net-next] vxlan: Correct path typo in comment

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: <5501983C.50006@cogentembedded.com>
Date:	Thu, 12 Mar 2015 16:44:28 +0300
From:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To:	Simon Horman <simon.horman@...ronome.com>,
	"David S. Miller" <davem@...emloft.net>
CC:	Tom Herbert <therbert@...gle.com>, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] vxlan: Correct path typo in comment

Hello.

On 3/12/2015 5:00 AM, Simon Horman wrote:

> Flags are used in the return path rather than the return patch.

    s/return/receive/?

> Fixes: af33c1adae1e ("vxlan: Eliminate dependency on UDP socket in transmit path")
> Signed-off-by: Simon Horman <simon.horman@...ronome.com>
[...]

> diff --git a/include/net/vxlan.h b/include/net/vxlan.h
> index eabd3a0..9564b77 100644
> --- a/include/net/vxlan.h
> +++ b/include/net/vxlan.h
> @@ -130,7 +130,7 @@ struct vxlan_sock {
>   #define VXLAN_F_GBP			0x800
>   #define VXLAN_F_REMCSUM_NOPARTIAL	0x1000
>
> -/* Flags that are used in the receive patch. These flags must match in
> +/* Flags that are used in the receive path. These flags must match in
>    * order for a socket to be shareable
>    */
>   #define VXLAN_F_RCV_FLAGS		(VXLAN_F_GBP |			\

WBR, Sergei

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