netdev - Re: [PATCH iproute2-next 2/2] f_flower: implement pfcp opts

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: <20240410085319.2cc6a94a@hermes.local>
Date: Wed, 10 Apr 2024 08:53:19 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Wojciech Drewek <wojciech.drewek@...el.com>
Cc: netdev@...r.kernel.org, dsahern@...il.com
Subject: Re: [PATCH iproute2-next 2/2] f_flower: implement pfcp opts

On Wed, 10 Apr 2024 12:14:40 +0200
Wojciech Drewek <wojciech.drewek@...el.com> wrote:

> +pfcp_opts
> +.I OPTIONS
> +doesn't support multiple options, and it consists of a key followed by a slash
> +and corresponding mask. If the mask is missing, \fBtc\fR assumes a full-length
> +match. The option can be described in the form TYPE:SEID/TYPE_MASK:SEID_MASK
> +where TYPE is represented as a 8bit number, SEID is represented by 64bit, both
> +of them are in hex.

Best practices in English writing style is to make all clauses have similar
starting phrase.

Existing paragraph here is a mess already, so not unique to this.
That part of tc-flower man page needs some grammar fixes, as well
as being broken up.