From: David Laight <david.laight.linux@gmail.com>
To: Adrien Reynard <reynard.adrien.08@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] docs: fix repeated word 'in' in networking documentation
Date: Sat, 9 May 2026 22:07:10 +0100 [thread overview]
Message-ID: <20260509220710.05e78cfe@pumpkin> (raw)
In-Reply-To: <20260509143103.16558-1-reynard.adrien.08@gmail.com>
On Sat, 9 May 2026 16:31:03 +0200
Adrien Reynard <reynard.adrien.08@gmail.com> wrote:
> Remove duplicated word 'in' in networking/switchdev.rst.
Nak
>
> Signed-off-by: Adrien Reynard <reynard.adrien.08@gmail.com>
> ---
> Documentation/networking/switchdev.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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
prev parent reply other threads:[~2026-05-09 21:07 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
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 [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=20260509220710.05e78cfe@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=reynard.adrien.08@gmail.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 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.