All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Bharat Bhushan <bbhushan2@marvell.com>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	Chris Snook <chris.snook@gmail.com>,
	Eric Dumazet <edumazet@google.com>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	GR-Linux-NIC-Dev@marvell.com,
	Geetha sowjanya <gakula@marvell.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Jian Shen <shenjian15@huawei.com>,
	Jijie Shao <shaojijie@huawei.com>,
	Manish Chopra <manishc@marvell.com>,
	Marcin Wojtas <marcin.s.wojtas@gmail.com>,
	Paolo Abeni <pabeni@redhat.com>, Rahul Verma <rahulv@marvell.com>,
	Ratheesh Kannoth <rkannoth@marvell.com>,
	Russell King <linux@armlinux.org.uk>,
	Shahed Shaikh <shshaikh@marvell.com>,
	Shuah Khan <shuah@kernel.org>,
	Subbaraya Sundeep <sbhatta@marvell.com>,
	Sudarsana Kalluru <skalluru@marvell.com>,
	Sunil Goutham <sgoutham@marvell.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-parisc@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 03/10] net: broadcom: fix typos in comments
Date: Thu, 10 Sep 2026 11:28:22 +0100	[thread overview]
Message-ID: <20260910102822.GV40544@horms.kernel.org> (raw)
In-Reply-To: <20260908052602.27497-4-hemanth.selam@gmail.com>

On Tue, Sep 08, 2026 at 10:55:55AM +0530, Hemanth Selam wrote:
> Fix misspellings in comments, found with scripts/checkpatch.pl using
> the misspelling list in scripts/spelling.txt.  Comments only, no code
> changes.
> 
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>

...

> diff --git a/drivers/net/ethernet/broadcom/bnx2x/bnx2x.h b/drivers/net/ethernet/broadcom/bnx2x/bnx2x.h
> index 9580ab83d387..28ea4a33f245 100644
> --- a/drivers/net/ethernet/broadcom/bnx2x/bnx2x.h
> +++ b/drivers/net/ethernet/broadcom/bnx2x/bnx2x.h
> @@ -280,7 +280,7 @@ enum {
>   * (db_msg_sz 1 << 7 * cid + 0x40 DPM offset) it can come up with a valid number
>   * We must avoid coming up with cid 8 for iscsi since according to this method
>   * the designated UIO cid will come out 0 and it has a special handling for that
> - * case which doesn't suit us. Therefore will will cieling to closes cid which
> + * case which doesn't suit us. Therefore will cieling to closes cid which

I'm struggling a little with cieling being used as a verb.
But that aside, I think the correct spelling is ceiling.

And perhaps closes should be closest?

Maybe we can fix these while we are here?

>   * has least signigifcant nibble 8 and if it is 8 we will move forward to 0x18.
>   */
>  

...

I don't mind if you don't want to re-spin the entire series just because
of this. Either way:

Reviewed-by: Simon Horman <horms@kernel.org>


  reply	other threads:[~2026-09-10 10:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08  5:25 [PATCH net-next v3 00/10] net: fix typos and repeated words in comments Hemanth Selam
2026-09-08  5:25 ` [PATCH net-next v3 01/10] net: llc: fix repeated word 'all' in comment Hemanth Selam
2026-09-08  5:25 ` [PATCH net-next v3 02/10] selftests: net: fix repeated word 'use' " Hemanth Selam
2026-09-08  5:25 ` [PATCH net-next v3 03/10] net: broadcom: fix typos in comments Hemanth Selam
2026-09-10 10:28   ` Simon Horman [this message]
2026-09-08  5:25 ` [PATCH net-next v3 04/10] net: cavium: " Hemanth Selam
2026-09-10 10:30   ` Simon Horman
2026-09-08  5:25 ` [PATCH net-next v3 05/10] net: qlogic: " Hemanth Selam
2026-09-10 10:31   ` Simon Horman
2026-09-08  5:25 ` [PATCH net-next v3 06/10] net: fddi: " Hemanth Selam
2026-09-10 10:33   ` Simon Horman
2026-09-08  5:25 ` [PATCH net-next v3 07/10] net: marvell: " Hemanth Selam
2026-09-08  5:35   ` Ratheesh Kannoth
2026-09-08 12:04     ` Andrew Lunn
2026-09-08  5:26 ` [PATCH net-next v3 08/10] net: hisilicon: " Hemanth Selam
2026-09-10 10:34   ` Simon Horman
2026-09-08  5:26 ` [PATCH net-next v3 09/10] net: atheros: " Hemanth Selam
2026-09-10 10:37   ` Simon Horman
2026-09-08  5:26 ` [PATCH net-next v3 10/10] net: dec: " Hemanth Selam
2026-09-10 10:37   ` Simon Horman
2026-09-10 15:40 ` [PATCH net-next v3 00/10] net: fix typos and repeated words " patchwork-bot+netdevbpf

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=20260910102822.GV40544@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=GR-Linux-NIC-Dev@marvell.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bbhushan2@marvell.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=chris.snook@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=gakula@marvell.com \
    --cc=hemanth.selam@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=manishc@marvell.com \
    --cc=marcin.s.wojtas@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rahulv@marvell.com \
    --cc=rkannoth@marvell.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.com \
    --cc=shaojijie@huawei.com \
    --cc=shenjian15@huawei.com \
    --cc=shshaikh@marvell.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 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.