From: Quentin Monnet <quentin@isovalent.com>
To: Alejandro Colomar <alx.manpages@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
bpf@vger.kernel.org, Jakub Wilk <jwilk@jwilk.net>,
Jesper Dangaard Brouer <brouer@redhat.com>,
linux-man@vger.kernel.org
Subject: Re: [PATCH bpf-next v3] bpf: Fix a few typos in BPF helpers documentation
Date: Fri, 26 Aug 2022 10:44:46 +0100 [thread overview]
Message-ID: <c94959da-67f6-da66-1d46-ae9dfdc0e674@isovalent.com> (raw)
In-Reply-To: <ebbae976-b452-c359-fd67-5b0511c3ef10@gmail.com>
On 25/08/2022 23:12, Alejandro Colomar wrote:
> Hi Quentin,
>
>> - * ctx. Providing an *len_diff* adjustment that is larger than
>> the
>
> I just noticed: groff(1) uses double spaces after an end-of-sentence
> period. Otherwise, it is understood as something like initials, or an
> abbreviature, and it causes some issues. Please check the whole
> document, as I've seen a mix of styles.
>
> Search for something like '.\. [^ ]'
This is a strange restriction in my opinion, but I can look into this as
a follow-up. I've not noticed issues with the rendered page so far, out
of curiosity what issues are we talking about?
Also before that, it would be good to sync and see what other formatting
elements need be addressed on the page, so we can fix them in a batch
rather than submitting them one after the other like we're doing.
Quentin
next prev parent reply other threads:[~2022-08-26 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 22:08 [PATCH bpf-next v3] bpf: Fix a few typos in BPF helpers documentation Quentin Monnet
2022-08-25 22:12 ` Alejandro Colomar
2022-08-26 9:44 ` Quentin Monnet [this message]
2022-08-26 17:17 ` Alejandro Colomar
2022-08-27 5:20 ` patchwork-bot+netdevbpf
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=c94959da-67f6-da66-1d46-ae9dfdc0e674@isovalent.com \
--to=quentin@isovalent.com \
--cc=alx.manpages@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jwilk@jwilk.net \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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