From: Wojciech Drewek <wojciech.drewek@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <netdev@vger.kernel.org>, <dsahern@gmail.com>
Subject: Re: [PATCH iproute2-next 2/2] f_flower: implement pfcp opts
Date: Thu, 11 Apr 2024 13:32:10 +0200 [thread overview]
Message-ID: <94297026-c760-450c-aaee-ad0034c1431d@intel.com> (raw)
In-Reply-To: <20240410085319.2cc6a94a@hermes.local>
On 10.04.2024 17:53, Stephen Hemminger wrote:
> On Wed, 10 Apr 2024 12:14:40 +0200
> Wojciech Drewek <wojciech.drewek@intel.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.
pfcp_opts
.I OPTIONS
doesn't support multiple options. 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
TYPE and SEID are provided in hex.
Does it look better?
>
> 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.
next prev parent reply other threads:[~2024-04-11 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 10:14 [PATCH iproute2-next 0/2] PFCP support Wojciech Drewek
2024-04-10 10:14 ` [PATCH iproute2-next 1/2] ip: PFCP device support Wojciech Drewek
2024-04-10 10:14 ` [PATCH iproute2-next 2/2] f_flower: implement pfcp opts Wojciech Drewek
2024-04-10 15:53 ` Stephen Hemminger
2024-04-11 11:32 ` Wojciech Drewek [this message]
2024-04-12 14:41 ` David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94297026-c760-450c-aaee-ad0034c1431d@intel.com \
--to=wojciech.drewek@intel.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).