From: Andrew Lunn <andrew@lunn.ch>
To: Wang Zihan <3772548978@qq.com>
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-media@vger.kernel.org, linux-um@lists.infradead.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
skhan@linuxfoundation.org, mchehab@kernel.org, richard@nod.at,
anton.ivanov@cambridgegreys.com, johannes@sipsolutions.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix duplicated words
Date: Sat, 2 May 2026 16:16:01 +0200 [thread overview]
Message-ID: <918f7cdc-c0bc-4cbb-8385-ca0ddb2180c1@lunn.ch> (raw)
In-Reply-To: <tencent_B1D6CBBF95486E31D04C2E1B92F5E605A307@qq.com>
On Sat, May 02, 2026 at 07:19:16PM +0800, Wang Zihan wrote:
> Remove duplicated words in three documentation files:
> - "in in" -> "in" (switchdev.rst)
> - "The the" -> "The" (dmx-reqbufs.rst)
> - "on on" -> "on" (user_mode_linux_howto_v2.rst)
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
* don’t repost your patches within one 24h period
We have already told you one of the fixes is wrong, but you did not
wait 24 hours, so have not see our feedback.
Also, in general when using a tool, assume it is wrong, and convince
yourself it is correct, before making a change. "The the in this
sentence is the subject." What does the bot make of that? Can you
convince yourself the bot is correct?
Andrew
---
pw-bot: cr
prev parent reply other threads:[~2026-05-02 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 11:19 [PATCH] Documentation: Fix duplicated words Wang Zihan
2026-05-02 12:01 ` Björn Persson
2026-05-02 14:16 ` Andrew Lunn [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=918f7cdc-c0bc-4cbb-8385-ca0ddb2180c1@lunn.ch \
--to=andrew@lunn.ch \
--cc=3772548978@qq.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richard@nod.at \
--cc=skhan@linuxfoundation.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