From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Manuel Cortez <mdjesuscv@gmail.com>,
linux-doc@vger.kernel.org
Cc: corbet@lwn.net
Subject: Re: [PATCH] docs: fix typos and duplicated words across documentation
Date: Sun, 5 Apr 2026 12:01:12 +0700 [thread overview]
Message-ID: <adHsmPH7sehjq0AK@archie.me> (raw)
In-Reply-To: <8e489ff9-e9f8-4924-ad92-a1dbd6d33121@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On Sat, Apr 04, 2026 at 08:16:05PM -0700, Randy Dunlap wrote:
> Hi,
>
> This last one is a little awkward as is but dropping one "in" doesn't help it --
> it harms it (i.e., it's correct as is but could possibly be improved.)
>
> > 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
I think it can be reworded as "The driver will track movements to locate
the port's position in the overall topology ...".
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-04-05 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-05 3:03 [PATCH] docs: fix typos and duplicated words across documentation Manuel Cortez
2026-04-05 3:16 ` Randy Dunlap
2026-04-05 5:01 ` Bagas Sanjaya [this message]
2026-04-06 3:03 ` [PATCH v2] " Manuel Cortez
2026-04-06 5:00 ` Randy Dunlap
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=adHsmPH7sehjq0AK@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=mdjesuscv@gmail.com \
--cc=rdunlap@infradead.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