From: Christian Lamparter <chunkeey@gmail.com>
To: Hemanth Selam <hemanth.selam@gmail.com>,
Jeff Johnson <jjohnson@kernel.org>,
Jiri Slaby <jirislaby@kernel.org>,
Nick Kossifidis <mickflemm@gmail.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Stanislav Yakovlev <stas.yakovlev@gmail.com>,
Stanislaw Gruszka <stf_xl@wp.pl>, Michael Buesch <m@bues.ch>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
b43-dev@lists.infradead.org, brcm80211@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com,
libertas-dev@lists.infradead.org
Subject: Re: [PATCH] wifi: fix typos in comments
Date: Sun, 6 Sep 2026 12:44:12 +0200 [thread overview]
Message-ID: <d739eb56-b37d-4056-abf2-c3a4c9ba8662@gmail.com> (raw)
In-Reply-To: <20260904124353.6183-1-hemanth.selam@gmail.com>
On 9/4/26 2:43 PM, 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>
Sure, for the p54 and carl9170 parts:
Acked-by: Christian Lamparter <chunkeey@gmail.com>
Does anyone know what ever happened to the trivial-patches?
https://www.kernel.org/pub/linux/kernel/people//rusty/trivial/template-index.html
Is this still going?
> ---
> drivers/net/wireless/ath/carl9170/fwcmd.h | 2 +-
> drivers/net/wireless/ath/carl9170/main.c | 8 ++++----
> drivers/net/wireless/broadcom/b43/b43.h | 8 ++++----
> drivers/net/wireless/intersil/p54/p54pci.c | 2 +-
>
> diff --git a/drivers/net/wireless/ath/carl9170/fwcmd.h b/drivers/net/wireless/ath/carl9170/fwcmd.h
> index e5bcc364f088..40554e4bd149 100644
> --- a/drivers/net/wireless/ath/carl9170/fwcmd.h
> +++ b/drivers/net/wireless/ath/carl9170/fwcmd.h
> @@ -69,7 +69,7 @@ enum carl9170_cmd_oids {
> CARL9170_CMD_FREQ_START = 0x23,
> CARL9170_CMD_PSM = 0x24,
>
> - /* Asychronous command flag */
> + /* Asynchronous command flag */
> CARL9170_CMD_ASYNC_FLAG = 0x40,
> CARL9170_CMD_WREG_ASYNC = (CARL9170_CMD_WREG |
> CARL9170_CMD_ASYNC_FLAG),
> diff --git a/drivers/net/wireless/ath/carl9170/main.c b/drivers/net/wireless/ath/carl9170/main.c
> index 61c7a1288743..21d8798dedb5 100644
> --- a/drivers/net/wireless/ath/carl9170/main.c
> +++ b/drivers/net/wireless/ath/carl9170/main.c
> @@ -575,7 +575,7 @@ static int carl9170_init_interface(struct ar9170 *ar,
> * NOTE: If the previous main interface has already
> * disabled hw crypto offload, we have to keep this
> * previous disable_offload setting as it was.
> - * Altough ideally, we should notify mac80211 and tell
> + * Although ideally, we should notify mac80211 and tell
> * it to forget about any HW crypto offload for now.
> */
> ar->disable_offload |= ((vif->type != NL80211_IFTYPE_STATION) &&
> @@ -677,12 +677,12 @@ static int carl9170_op_add_interface(struct ieee80211_hw *hw,
> if (old_main) {
> /* We end up in here, if the main interface is being replaced.
> * Put the new main interface at the HEAD of the list and the
> - * previous inteface will automatically become second in line.
> + * previous interface will automatically become second in line.
> */
> list_add_rcu(&vif_priv->list, &ar->vif_list);
> } else {
> - /* Add new inteface. If the list is empty, it will become the
> - * main inteface, otherwise it will be slave.
> + /* Add new interface. If the list is empty, it will become the
> + * main interface, otherwise it will be slave.
> */
> list_add_tail_rcu(&vif_priv->list, &ar->vif_list);
> }
> diff --git a/drivers/net/wireless/intersil/p54/p54pci.c b/drivers/net/wireless/intersil/p54/p54pci.c
> index 6588f5477762..68e929fa213c 100644
> --- a/drivers/net/wireless/intersil/p54/p54pci.c
> +++ b/drivers/net/wireless/intersil/p54/p54pci.c
> @@ -534,7 +534,7 @@ static void p54p_firmware_step2(const struct firmware *fw,
> /*
> * This will indirectly result in a call to p54p_remove.
> * Hence, we don't need to bother with freeing any
> - * allocated ressources at all.
> + * allocated resources at all.
> */
> device_release_driver(&pdev->dev);
>
next prev parent reply other threads:[~2026-09-06 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 12:43 [PATCH] wifi: fix typos in comments Hemanth Selam
2026-09-04 13:24 ` Arend van Spriel
2026-09-06 10:44 ` Christian Lamparter [this message]
2026-09-07 13:00 ` Joshua Peisach
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=d739eb56-b37d-4056-abf2-c3a4c9ba8662@gmail.com \
--to=chunkeey@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=hemanth.selam@gmail.com \
--cc=jirislaby@kernel.org \
--cc=jjohnson@kernel.org \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
--cc=mcgrof@kernel.org \
--cc=mickflemm@gmail.com \
--cc=stas.yakovlev@gmail.com \
--cc=stf_xl@wp.pl \
/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