linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Borkmann <daniel@iogearbox.net>,
	Mahmoud Abumandour <ma.mandourr@gmail.com>,
	linux-doc@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	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>,
	Nathan Chancellor <nathan@kernel.org>,
	bpf@vger.kernel.org
Subject: Re: [PATCH] docs/bpf: Fix most/least significant bit typos
Date: Mon, 21 Mar 2022 10:12:45 -0600	[thread overview]
Message-ID: <877d8nnv2a.fsf@meer.lwn.net> (raw)
In-Reply-To: <c40b0d55-e3c9-2027-765b-a4868ae16795@iogearbox.net>

Daniel Borkmann <daniel@iogearbox.net> writes:

> On 3/19/22 5:43 PM, Mahmoud Abumandour wrote:
>> The LSB and MSB acronyms should not be followed by the word "bits". This
>> fixes this issue and uses the full phrases "most/least significant bits"
>> for better readibility.
>> 
>> Signed-off-by: Mahmoud Abumandour <ma.mandourr@gmail.com>
>
> What "issue" is being fixed here? Why would you not use the acronyms? It's fine
> as-is, not applying it.

I *think* that the nit being picked here is that the word "bits" after
an acronym like MSB is redundant...

jon

      reply	other threads:[~2022-03-21 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19 16:43 [PATCH] docs/bpf: Fix most/least significant bit typos Mahmoud Abumandour
2022-03-21 15:19 ` Daniel Borkmann
2022-03-21 16:12   ` Jonathan Corbet [this message]

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=877d8nnv2a.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=ma.mandourr@gmail.com \
    --cc=nathan@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).