From: Jonathan Corbet <corbet@lwn.net>
To: Haoyang Liu <tttturtleruss@hust.edu.cn>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>
Cc: hust-os-kernel-patches@googlegroups.com,
Haoyang Liu <tttturtleruss@hust.edu.cn>,
kasan-dev@googlegroups.com, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/dev-tools: fix a typo
Date: Thu, 17 Oct 2024 09:41:04 -0600 [thread overview]
Message-ID: <877ca63ffz.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20241015140159.8082-1-tttturtleruss@hust.edu.cn>
Haoyang Liu <tttturtleruss@hust.edu.cn> writes:
> fix a typo in dev-tools/kmsan.rst
>
> Signed-off-by: Haoyang Liu <tttturtleruss@hust.edu.cn>
> ---
> Documentation/dev-tools/kmsan.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/dev-tools/kmsan.rst b/Documentation/dev-tools/kmsan.rst
> index 6a48d96c5c85..0dc668b183f6 100644
> --- a/Documentation/dev-tools/kmsan.rst
> +++ b/Documentation/dev-tools/kmsan.rst
> @@ -133,7 +133,7 @@ KMSAN shadow memory
> -------------------
>
> KMSAN associates a metadata byte (also called shadow byte) with every byte of
> -kernel memory. A bit in the shadow byte is set iff the corresponding bit of the
> +kernel memory. A bit in the shadow byte is set if the corresponding bit of the
> kernel memory byte is uninitialized. Marking the memory uninitialized (i.e.
> setting its shadow bytes to ``0xff``) is called poisoning, marking it
> initialized (setting the shadow bytes to ``0x00``) is called unpoisoning.
So I have applied this, since "iff" is clearly confusing to a lot of
readers even iff it's correct.
Thanks,
jon
prev parent reply other threads:[~2024-10-17 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 14:01 [PATCH] docs/dev-tools: fix a typo Haoyang Liu
2024-10-15 14:10 ` Dongliang Mu
2024-10-15 14:32 ` Marco Elver
2024-10-16 13:30 ` Dan Carpenter
2024-10-16 13:34 ` Alexander Potapenko
2024-10-16 14:52 ` Jonathan Corbet
2024-10-16 21:18 ` Shuah Khan
2024-10-17 15:41 ` 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=877ca63ffz.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tttturtleruss@hust.edu.cn \
--cc=workflows@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.