From: Wang Liang <wangliang74@huawei.com>
To: <miriam.rachel.korenblit@intel.com>, <johannes.berg@intel.com>,
<ganjie182@gmail.com>, <emmanuel.grumbach@intel.com>,
<avraham.stern@intel.com>
Cc: <yuehaibing@huawei.com>, <zhangchangzhong@huawei.com>,
<wangliang74@huawei.com>, <linux-wireless@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH wireless] wifi: iwlwifi:: fix spelling errors
Date: Mon, 24 Mar 2025 11:00:21 +0800 [thread overview]
Message-ID: <20250324030021.2296493-1-wangliang74@huawei.com> (raw)
Fix some spelling errors in comments:
- configuraiton -> configuration
- notificaiton -> notification
No functional changes.
Signed-off-by: Wang Liang <wangliang74@huawei.com>
---
drivers/net/wireless/intel/iwlwifi/fw/error-dump.h | 2 +-
drivers/net/wireless/intel/iwlwifi/mei/iwl-mei.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/intel/iwlwifi/fw/error-dump.h b/drivers/net/wireless/intel/iwlwifi/fw/error-dump.h
index 3af275133da0..b4528668478d 100644
--- a/drivers/net/wireless/intel/iwlwifi/fw/error-dump.h
+++ b/drivers/net/wireless/intel/iwlwifi/fw/error-dump.h
@@ -364,7 +364,7 @@ struct iwl_fw_ini_error_dump_register {
* struct iwl_fw_ini_dump_cfg_name - configuration name
* @image_type: image type the configuration is related to
* @cfg_name_len: length of the configuration name
- * @cfg_name: name of the configuraiton
+ * @cfg_name: name of the configuration
*/
struct iwl_fw_ini_dump_cfg_name {
__le32 image_type;
diff --git a/drivers/net/wireless/intel/iwlwifi/mei/iwl-mei.h b/drivers/net/wireless/intel/iwlwifi/mei/iwl-mei.h
index 2081775e0ec9..71adbe844060 100644
--- a/drivers/net/wireless/intel/iwlwifi/mei/iwl-mei.h
+++ b/drivers/net/wireless/intel/iwlwifi/mei/iwl-mei.h
@@ -475,7 +475,7 @@ void iwl_mei_device_state(bool up);
int iwl_mei_pldr_req(void);
/**
- * iwl_mei_alive_notif() - must be called when alive notificaiton is received
+ * iwl_mei_alive_notif() - must be called when alive notification is received
* @success: true if received alive notification, false if waiting for the
* notificaiton timed out.
*/
--
2.34.1
next reply other threads:[~2025-03-24 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 3:00 Wang Liang [this message]
2025-03-24 9:11 ` Johannes Berg
2025-03-31 10:21 ` Korenblit, Miriam Rachel
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=20250324030021.2296493-1-wangliang74@huawei.com \
--to=wangliang74@huawei.com \
--cc=avraham.stern@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=ganjie182@gmail.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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®