From: Hemanth Selam <hemanth.selam@gmail.com>
To: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew@lunn.ch>,
Sudarsana Kalluru <skalluru@marvell.com>,
Manish Chopra <manishc@marvell.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Simon Horman <horms@kernel.org>,
Edward Cree <ecree.xilinx@gmail.com>,
Shuah Khan <shuah@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-net-drivers@amd.com, linux-kselftest@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: [PATCH v2 4/6] net: sfc: fix repeated word 'the' in comment
Date: Mon, 7 Sep 2026 10:16:33 +0530 [thread overview]
Message-ID: <20260907044635.7141-5-hemanth.selam@gmail.com> (raw)
In-Reply-To: <20260907044635.7141-1-hemanth.selam@gmail.com>
Drop the repeated "the", reported by scripts/checkpatch.pl. Only touches
a comment, no code changes.
The bitfield.h hunks from v1 are gone: "the relevant bits filled in in
the range" is correct as it stands, since "filled in" ends the clause and
"in the range" begins the next.
Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
drivers/net/ethernet/sfc/mcdi_pcol.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/sfc/mcdi_pcol.h b/drivers/net/ethernet/sfc/mcdi_pcol.h
index b00e7c100566..976a96459075 100644
--- a/drivers/net/ethernet/sfc/mcdi_pcol.h
+++ b/drivers/net/ethernet/sfc/mcdi_pcol.h
@@ -9560,7 +9560,7 @@
* DMA synchronizaion. Always the last entry in the DMA buffer and set to the
* same value as GENERATION_START. The host driver must compare the
* GENERATION_START and GENERATION_END values to verify that the DMA buffer is
- * consistent upon copying the the DMA buffer. If they do not match, it means
+ * consistent upon copying the DMA buffer. If they do not match, it means
* that new DMA transfer has started while the host driver was copying the DMA
* buffer. In this case, the host driver must repeat the copy operation.
*/
next prev parent reply other threads:[~2026-09-07 4:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 4:46 [PATCH v2 0/6] net: fix typos and repeated words in comments Hemanth Selam
2026-09-07 4:46 ` [PATCH v2 1/6] net: fix typos " Hemanth Selam
2026-09-07 12:49 ` Jijie Shao
2026-09-07 12:52 ` Andrew Lunn
2026-09-07 15:37 ` Edward Cree
2026-09-07 4:46 ` [PATCH v2 2/6] net: broadcom: fix repeated word 'will' in comment Hemanth Selam
2026-09-07 4:46 ` [PATCH v2 3/6] net: llc: fix repeated word 'all' " Hemanth Selam
2026-09-07 12:46 ` Andrew Lunn
2026-09-07 4:46 ` Hemanth Selam [this message]
2026-09-07 12:46 ` [PATCH v2 4/6] net: sfc: fix repeated word 'the' " Andrew Lunn
2026-09-07 15:38 ` Edward Cree
2026-09-07 4:46 ` [PATCH v2 5/6] selftests: net: fix repeated word 'use' " Hemanth Selam
2026-09-07 12:47 ` Andrew Lunn
2026-09-07 4:46 ` [PATCH v2 6/6] net: usb: fix repeated words in log messages Hemanth Selam
2026-09-07 12:49 ` Andrew Lunn
2026-09-08 5:25 ` Hemanth Selam
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=20260907044635.7141-5-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=linux-usb@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=skalluru@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®