From: "Ignacio Peña" <ignacio.pena87@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Ignacio Pena <ignacio.pena87@gmail.com>
Subject: [PATCH] block: Fix typo 'programm' -> 'program'
Date: Fri, 25 Jul 2025 00:14:16 -0400 [thread overview]
Message-ID: <20250725041416.73567-1-ignacio.pena87@gmail.com> (raw)
Fix spelling mistake.
No functional change.
Signed-off-by: Ignacio Pena <ignacio.pena87@gmail.com>
---
block/blk-crypto-profile.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/block/blk-crypto-profile.c b/block/blk-crypto-profile.c
index 81918f6e0..72462b6f4 100644
--- a/block/blk-crypto-profile.c
+++ b/block/blk-crypto-profile.c
@@ -237,7 +237,7 @@ EXPORT_SYMBOL_GPL(blk_crypto_keyslot_index);
* will be stored here. blk_crypto_put_keyslot() must be called
* later to release it. Otherwise, NULL will be stored here.
*
- * If the device has keyslots, this gets a keyslot that's been programmed with
+ * If the device has keyslots, this gets a keyslot that's been programed with
* the specified key. If the key is already in a slot, this reuses it;
* otherwise this waits for a slot to become idle and programs the key into it.
*
@@ -278,7 +278,7 @@ blk_status_t blk_crypto_get_keyslot(struct blk_crypto_profile *profile,
/*
* If we're here, that means there wasn't a slot that was
- * already programmed with the key. So try to program it.
+ * already programed with the key. So try to program it.
*/
if (!list_empty(&profile->idle_slots))
break;
@@ -412,7 +412,7 @@ int __blk_crypto_evict_key(struct blk_crypto_profile *profile,
* blk_crypto_reprogram_all_keys() - Re-program all keyslots.
* @profile: The crypto profile
*
- * Re-program all keyslots that are supposed to have a key programmed. This is
+ * Re-program all keyslots that are supposed to have a key programed. This is
* intended only for use by drivers for hardware that loses its keys on reset.
*
* Context: Process context. Takes and releases profile->lock.
--
2.50.1
next reply other threads:[~2025-07-25 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 4:14 Ignacio Peña [this message]
2025-07-25 14:57 ` Bart Van Assche
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=20250725041416.73567-1-ignacio.pena87@gmail.com \
--to=ignacio.pena87@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®