From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,vgoyal@redhat.com,dyoung@redhat.com,bhe@redhat.com,akpm@linux-foundation.org,thorsten.blum@linux.dev,akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] crash_dump-fix-typo-in-function-name-read_key_from_user_keying.patch removed from -mm tree
Date: Fri, 27 Mar 2026 21:24:54 -0700 [thread overview]
Message-ID: <20260328042454.84F2FC4CEF7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: crash_dump: fix typo in function name read_key_from_user_keying
has been removed from the -mm tree. Its filename was
crash_dump-fix-typo-in-function-name-read_key_from_user_keying.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Thorsten Blum <thorsten.blum@linux.dev>
Subject: crash_dump: fix typo in function name read_key_from_user_keying
Date: Sat, 28 Feb 2026 00:04:21 +0100
The function read_key_from_user_keying() is missing an 'r' in its name.
Fix the typo by renaming it to read_key_from_user_keyring().
Link: https://lkml.kernel.org/r/20260227230422.859423-1-thorsten.blum@linux.dev
Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Acked-by: Baoquan He <bhe@redhat.com>
Cc: Dave Young <dyoung@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/crash_dump_dm_crypt.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/kernel/crash_dump_dm_crypt.c~crash_dump-fix-typo-in-function-name-read_key_from_user_keying
+++ a/kernel/crash_dump_dm_crypt.c
@@ -139,7 +139,7 @@ static int restore_dm_crypt_keys_to_thre
return 0;
}
-static int read_key_from_user_keying(struct dm_crypt_key *dm_key)
+static int read_key_from_user_keyring(struct dm_crypt_key *dm_key)
{
const struct user_key_payload *ukp;
struct key *key;
@@ -387,7 +387,7 @@ static int build_keys_header(void)
strscpy(keys_header->keys[i].key_desc, key->description,
KEY_DESC_MAX_LEN);
- r = read_key_from_user_keying(&keys_header->keys[i]);
+ r = read_key_from_user_keyring(&keys_header->keys[i]);
if (r != 0) {
kexec_dprintk("Failed to read key %s\n",
keys_header->keys[i].key_desc);
_
Patches currently in -mm which might be from thorsten.blum@linux.dev are
reply other threads:[~2026-03-28 4:24 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=20260328042454.84F2FC4CEF7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=mm-commits@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
--cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.