From: David Laight <david.laight.linux@gmail•com>
To: Adrien Reynard <reynard.adrien.08@gmail•com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail•com>,
Alexander Potapenko <glider@google•com>,
Andrey Konovalov <andreyknvl@gmail•com>,
Dmitry Vyukov <dvyukov@google•com>,
Vincenzo Frascino <vincenzo.frascino@arm•com>,
Jonathan Corbet <corbet@lwn•net>,
Shuah Khan <skhan@linuxfoundation•org>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
Simon Horman <horms@kernel•org>,
Richard Weinberger <richard@nod•at>,
Anton Ivanov <anton.ivanov@cambridgegreys•com>,
Johannes Berg <johannes@sipsolutions•net>,
kasan-dev@googlegroups•com (open list:KASAN),
workflows@vger•kernel.org (open list:DOCUMENTATION PROCESS),
linux-doc@vger•kernel.org (open list:DOCUMENTATION),
linux-kernel@vger•kernel.org (open list),
netdev@vger•kernel.org (open list:NETWORKING [GENERAL]),
linux-um@lists•infradead.org (open list:USER-MODE LINUX (UML))
Subject: Re: [PATCH 4/5] docs: fix repeated prepositions across documentation
Date: Fri, 8 May 2026 19:28:55 +0100 [thread overview]
Message-ID: <20260508192855.3b024c83@pumpkin> (raw)
In-Reply-To: <20260508163804.16267-1-reynard.adrien.08@gmail.com>
On Fri, 8 May 2026 18:38:03 +0200
Adrien Reynard <reynard.adrien.08@gmail•com> wrote:
Nope, all these are correct as is.
I'm not looking at any more.
> Signed-off-by: Adrien Reynard <reynard.adrien.08@gmail•com>
> ---
> Documentation/dev-tools/kasan.rst | 2 +-
> Documentation/networking/switchdev.rst | 2 +-
> Documentation/virt/uml/user_mode_linux_howto_v2.rst | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/dev-tools/kasan.rst b/Documentation/dev-tools/kasan.rst
> index 4968b2aa60c8..3a8bd40ad905 100644
> --- a/Documentation/dev-tools/kasan.rst
> +++ b/Documentation/dev-tools/kasan.rst
> @@ -392,7 +392,7 @@ reserved to tag freed memory regions.
> If the hardware does not support MTE (pre ARMv8.5), Hardware Tag-Based KASAN
> will not be enabled. In this case, all KASAN boot parameters are ignored.
>
> -Note that enabling CONFIG_KASAN_HW_TAGS always results in in-kernel TBI being
> +Note that enabling CONFIG_KASAN_HW_TAGS always results in-kernel TBI being
> enabled. Even when ``kasan.mode=off`` is provided or when the hardware does not
> support MTE (but supports TBI).
>
> diff --git a/Documentation/networking/switchdev.rst b/Documentation/networking/switchdev.rst
> index 2966b7122f05..948bce44ca9b 100644
> --- a/Documentation/networking/switchdev.rst
> +++ b/Documentation/networking/switchdev.rst
> @@ -162,7 +162,7 @@ The switchdev driver can know a particular port's position in the topology by
> monitoring NETDEV_CHANGEUPPER notifications. For example, a port moved into a
> bond will see its upper master change. If that bond is moved into a bridge,
> the bond's upper master will change. And so on. The driver will track such
> -movements to know what position a port is in in the overall topology by
> +movements to know what position a port is in the overall topology by
> registering for netdevice events and acting on NETDEV_CHANGEUPPER.
>
> L2 Forwarding Offload
> diff --git a/Documentation/virt/uml/user_mode_linux_howto_v2.rst b/Documentation/virt/uml/user_mode_linux_howto_v2.rst
> index c37e8e594d12..7b08738c30aa 100644
> --- a/Documentation/virt/uml/user_mode_linux_howto_v2.rst
> +++ b/Documentation/virt/uml/user_mode_linux_howto_v2.rst
> @@ -1092,7 +1092,7 @@ be formatted as plain text.
>
> Developing always goes hand in hand with debugging. First of all,
> you can always run UML under gdb and there will be a whole section
> -later on on how to do that. That, however, is not the only way to
> +later on how to do that. That, however, is not the only way to
> debug a Linux kernel. Quite often adding tracing statements and/or
> using UML specific approaches such as ptracing the UML kernel process
> are significantly more informative.
next prev parent reply other threads:[~2026-05-08 18:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 16:38 [PATCH 4/5] docs: fix repeated prepositions across documentation Adrien Reynard
2026-05-08 17:23 ` Shuah Khan
2026-05-08 17:44 ` Randy Dunlap
2026-05-08 22:41 ` Andrew Lunn
2026-05-08 22:52 ` Randy Dunlap
2026-05-09 19:39 ` Andrew Lunn
2026-05-09 20:41 ` Randy Dunlap
2026-05-08 18:28 ` David Laight [this message]
2026-05-09 14:31 ` [PATCH v2 4/4] docs: fix repeated word 'in' in networking documentation Adrien Reynard
2026-05-09 21:07 ` David Laight
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=20260508192855.3b024c83@pumpkin \
--to=david.laight.linux@gmail$(echo .)com \
--cc=andreyknvl@gmail$(echo .)com \
--cc=anton.ivanov@cambridgegreys$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=dvyukov@google$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=glider@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=johannes@sipsolutions$(echo .)net \
--cc=kasan-dev@googlegroups$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-um@lists$(echo .)infradead.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=reynard.adrien.08@gmail$(echo .)com \
--cc=richard@nod$(echo .)at \
--cc=ryabinin.a.a@gmail$(echo .)com \
--cc=skhan@linuxfoundation$(echo .)org \
--cc=vincenzo.frascino@arm$(echo .)com \
--cc=workflows@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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