All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jijie Shao <shaojijie@huawei.com>
To: Hemanth Selam <hemanth.selam@gmail.com>,
	"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: <shaojijie@huawei.com>, <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: Re: [PATCH v2 1/6] net: fix typos in comments
Date: Mon, 7 Sep 2026 20:49:10 +0800	[thread overview]
Message-ID: <bfc0de5b-9574-4376-a968-2ea9ea1f06b0@huawei.com> (raw)
In-Reply-To: <20260907044635.7141-2-hemanth.selam@gmail.com>


on 2026/9/7 12:46, Hemanth Selam wrote:
> Fix typos in comments, reported by scripts/checkpatch.pl using the
> misspelling list in scripts/spelling.txt.  Only touches comments, no code
> changes.
>
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>

For the hns and hns3 driver parts, the changes look good to me. Thanks,
Reviewed-by: Jijie Shao <shaojijie@huawei.com>

> ---
>   drivers/net/dsa/bcm_sf2_cfp.c                          |  2 +-
>   drivers/net/dsa/microchip/ksz_dcb.c                    |  2 +-

...

>   		pause_aneg_en:1,
> diff --git a/drivers/net/ethernet/hisilicon/hns/hns_dsaf_misc.c b/drivers/net/ethernet/hisilicon/hns/hns_dsaf_misc.c
> index 91391a49fcea..a59fd280a045 100644
> --- a/drivers/net/ethernet/hisilicon/hns/hns_dsaf_misc.c
> +++ b/drivers/net/ethernet/hisilicon/hns/hns_dsaf_misc.c
> @@ -591,7 +591,7 @@ static int hns_mac_config_sds_loopback(struct hns_mac_cb *mac_cb, bool en)
>   #define HILINK_ACCESS_SEL_CFG		0x40008
>   			/* hilink4 & hilink3 use the same xge training and
>   			 * xge u adaptor. There is a hilink access sel cfg
> -			 * register to select which one to be configed
> +			 * register to select which one to be configured
>   			 */
>   			if ((!HNS_DSAF_IS_DEBUG(mac_cb->dsaf_dev)) &&
>   			    (mac_cb->mac_id <= 3))
> diff --git a/drivers/net/ethernet/hisilicon/hns/hns_dsaf_ppe.c b/drivers/net/ethernet/hisilicon/hns/hns_dsaf_ppe.c
> index 5013beb4d282..408d36d85fb1 100644
> --- a/drivers/net/ethernet/hisilicon/hns/hns_dsaf_ppe.c
> +++ b/drivers/net/ethernet/hisilicon/hns/hns_dsaf_ppe.c
> @@ -139,7 +139,7 @@ static void hns_ppe_set_vlan_strip(struct hns_ppe_cb *ppe_cb, int en)
>   }
>   
>   /**
> - * hns_ppe_checksum_hw - set ppe checksum caculate
> + * hns_ppe_checksum_hw - set ppe checksum calculate
>    * @ppe_cb: ppe device
>    * @value: value
>    */
> diff --git a/drivers/net/ethernet/hisilicon/hns/hns_enet.c b/drivers/net/ethernet/hisilicon/hns/hns_enet.c
> index e905f10b894e..d819d2bb3450 100644
> --- a/drivers/net/ethernet/hisilicon/hns/hns_enet.c
> +++ b/drivers/net/ethernet/hisilicon/hns/hns_enet.c
> @@ -1230,7 +1230,7 @@ static void hns_nic_update_stats(struct net_device *netdev)
>   	h->dev->ops->update_stats(h, &netdev->stats);
>   }
>   
> -/* set mac addr if it is configed. or leave it to the AE driver */
> +/* set mac addr if it is configured. or leave it to the AE driver */
>   static void hns_init_mac_addr(struct net_device *ndev)
>   {
>   	struct hns_nic_priv *priv = netdev_priv(ndev);
> @@ -2317,7 +2317,7 @@ static int hns_nic_dev_probe(struct platform_device *pdev)
>   		ret = device_property_read_u32(dev, "port-id", &port_id);
>   		if (ret)
>   			goto out_read_prop_fail;
> -		/* for old dts, we need to caculate the port offset */
> +		/* for old dts, we need to calculate the port offset */
>   		port_id = port_id < HNS_SRV_OFFSET ? port_id + HNS_DEBUG_OFFSET
>   			: port_id - HNS_SRV_OFFSET;
>   	}
> diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c
> index e6af939c1c19..bf35f55f5b8f 100644
> --- a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c
> +++ b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c
> @@ -10527,7 +10527,7 @@ static int hclge_get_link_diagnosis_info(struct hnae3_handle *handle,
>   }
>   
>   /* After disable sriov, VF still has some config and info need clean,
> - * which configed by PF.
> + * which configured by PF.
>    */
>   static void hclge_clear_vport_vf_info(struct hclge_vport *vport, int vfid)
>   {
> diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_tm.c b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_tm.c
> index 00c3f2548bf6..bf533b8f46ae 100644
> --- a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_tm.c
> +++ b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_tm.c
> @@ -35,7 +35,7 @@ enum hclge_shaper_level {
>    * IR(Mbps) = -------------------------  *  CLOCK(1000Mbps)
>    *		Tick * (2 ^ IR_s)
>    *
> - * @return: 0: calculate sucessful, negative: fail
> + * @return: 0: calculate successful, negative: fail
>    */
>   static int hclge_shaper_para_calc(u32 ir, u8 shaper_level,
>   				  struct hclge_shaper_ir_para *ir_para,
> diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c b/drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c
> index 063a692c2b41..5d14d29b0296 100644
> --- a/drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c
> +++ b/drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c
> @@ -1880,7 +1880,7 @@ static void hclgevf_reset_service_task(struct hclgevf_dev *hdev)
>   		 * from PF as cmdq would be in unreliable state i.e. mailbox
>   		 * communication between PF and VF would be broken.
>   		 *
> -		 * if we are never geting into pending state it means either:
> +		 * if we are never getting into pending state it means either:
>   		 * 1. PF is not receiving our request which could be due to IMP
>   		 *    reset
>   		 * 2. PF is screwed

...


  reply	other threads:[~2026-09-07 12:49 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 [this message]
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 ` [PATCH v2 4/6] net: sfc: fix repeated word 'the' " Hemanth Selam
2026-09-07 12:46   ` 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=bfc0de5b-9574-4376-a968-2ea9ea1f06b0@huawei.com \
    --to=shaojijie@huawei.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=hemanth.selam@gmail.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 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.