From: Luis Chamberlain <mcgrof@kernel.org>
To: gregkh@linuxfoundation.org, russ.weight@linux.dev, dakr@redhat.com
Cc: mcgrof@kernel.org, song@kernel.org, mricon@kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH v2] firmware_loader: minor spelling fixes
Date: Wed, 4 Dec 2024 19:44:44 -0800 [thread overview]
Message-ID: <20241205034444.3498690-1-mcgrof@kernel.org> (raw)
Run codespell on the *.[ch] files for the firmware loader.
Reviewed-by: Russ Weight <russ.weight@linux.dev>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
This v2 is just a re-submit and add's Russ Weight's Reviewed-by.
This is intended to help kick test our CI as we explore some area of it.
drivers/base/firmware_loader/main.c | 2 +-
drivers/base/firmware_loader/sysfs_upload.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/base/firmware_loader/main.c b/drivers/base/firmware_loader/main.c
index 324a9a3c087a..1aa509756d3e 100644
--- a/drivers/base/firmware_loader/main.c
+++ b/drivers/base/firmware_loader/main.c
@@ -1528,7 +1528,7 @@ static void __device_uncache_fw_images(void)
* device_cache_fw_images() - cache devices' firmware
*
* If one device called request_firmware or its nowait version
- * successfully before, the firmware names are recored into the
+ * successfully before, the firmware names are recorded into the
* device's devres link list, so device_cache_fw_images can call
* cache_firmware() to cache these firmwares for the device,
* then the device driver can load its firmwares easily at
diff --git a/drivers/base/firmware_loader/sysfs_upload.c b/drivers/base/firmware_loader/sysfs_upload.c
index 829270067d16..7a838b30d8eb 100644
--- a/drivers/base/firmware_loader/sysfs_upload.c
+++ b/drivers/base/firmware_loader/sysfs_upload.c
@@ -209,7 +209,7 @@ static void fw_upload_main(struct work_struct *work)
/*
* Note: fwlp->remaining_size is left unmodified here to provide
* additional information on errors. It will be reinitialized when
- * the next firmeware upload begins.
+ * the next firmware upload begins.
*/
mutex_lock(&fw_lock);
fw_free_paged_buf(fw_sysfs->fw_priv);
--
2.45.2
reply other threads:[~2024-12-05 3:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241205034444.3498690-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=dakr@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mricon@kernel.org \
--cc=russ.weight@linux.dev \
--cc=song@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