Linux wireless drivers development
 help / color / mirror / Atom feed
From: Hemanth Selam <hemanth.selam@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH wireless-next v2 0/4] wifi: fix typos in comments
Date: Mon,  7 Sep 2026 15:23:44 +0530	[thread overview]
Message-ID: <20260907095348.26094-1-hemanth.selam@gmail.com> (raw)

Comment typos under wireless, split per component.  Found with scripts/checkpatch.pl using the
misspelling list in scripts/spelling.txt.  Comments only, no code
changes.

v1 went out with a bare [PATCH] and a "net:" subject prefix.  As
maintainer-netdev.rst asks, v2 designates the patches to a tree, and
each subject now names the component it touches instead of "net:".  The
series is rebased onto that tree; the diff is unchanged.

v1: https://lore.kernel.org/all/20260907061417.33729-1-hemanth.selam@gmail.com/


Hemanth Selam (4):
  wifi: nl80211: vendor-cmd: intel: fix typo "firwmare" in comment
  uapi: wireless: fix typos in comments
  wifi: mac80211: fix typo "capabilties" in comment
  wifi: mac80211: fix repeated word 'used' in comment

 include/net/mac80211.h                 | 2 +-
 include/uapi/linux/nl80211-vnd-intel.h | 2 +-
 include/uapi/linux/wireless.h          | 6 +++---
 net/mac80211/cfg.c                     | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)


             reply	other threads:[~2026-09-07  9:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  9:53 Hemanth Selam [this message]
2026-09-07  9:53 ` [PATCH wireless-next v2 1/4] wifi: nl80211: vendor-cmd: intel: fix typo "firwmare" in comment Hemanth Selam
2026-09-07  9:53 ` [PATCH wireless-next v2 2/4] uapi: wireless: fix typos in comments Hemanth Selam
2026-09-07  9:53 ` [PATCH wireless-next v2 3/4] wifi: mac80211: fix typo "capabilties" in comment Hemanth Selam
2026-09-07  9:53 ` [PATCH wireless-next v2 4/4] wifi: mac80211: fix repeated word 'used' " 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=20260907095348.26094-1-hemanth.selam@gmail.com \
    --to=hemanth.selam@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.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