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]
Date:	Sun, 07 Dec 2014 17:36:19 -0800
From:	John Fastabend <john.r.fastabend@...el.com>
To:	Simon Horman <simon.horman@...ronome.com>
CC:	netdev@...r.kernel.org
Subject: Re: [PATCH flow-net-next] net: flow: Correct spelling of action

On 12/07/2014 05:14 PM, Simon Horman wrote:
> Signed-off-by: Simon Horman <simon.horman@...ronome.com>
> ---
>  include/uapi/linux/if_flow.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/uapi/linux/if_flow.h b/include/uapi/linux/if_flow.h
> index 25aa744..9255990 100644
> --- a/include/uapi/linux/if_flow.h
> +++ b/include/uapi/linux/if_flow.h
> @@ -356,7 +356,7 @@ enum {
>   * @uid unique identifier for flow
>   * @priority priority to execute flow match/action in table
>   * @match null terminated set of match uids match criteria
> - * @actoin null terminated set of action uids to apply to match
> + * @action null terminated set of action uids to apply to match
>   *
>   * Flows must match all entries in match set.
>   */
> 

Great thanks Simon! Also I've added a bit so we can
distinguish between INGRESS pipelines and EGRESS pipelines
and a bunch of fixes to the netlink processing to check the
lengths correctly. I'll push those to my tree in the next day or
so. I'm also porting this to rocker switch now which I hope
should be ready in the next week for submitting.

Just to be clear this is against my git tree @

	https://github.com/jrfastab/flow-net-next/

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