From: Philipp Hahn <phahn-oss@avm.de>
To: linux-integrity@vger.kernel.org
Cc: Philipp Hahn <phahn-oss@avm.de>,
linux-kernel@vger.kernel.org, Nayna Jain <nayna@linux.ibm.com>,
Mimi Zohar <zohar@linux.ibm.com>
Subject: [PATCH] integrity: Fix spelling mistake TRUSTED_KEYRING
Date: Thu, 18 Dec 2025 11:31:22 +0100 [thread overview]
Message-ID: <4f736ebcd8a80c2e48c274cec027831d2986f792.1766053742.git.p.hahn@avm.de> (raw)
Fix minor spelling mistake "kerne{d -> l}".
Cc: Nayna Jain <nayna@linux.ibm.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>
Fixes: 9dc92c45177ab ("integrity: Define a trusted platform keyring")
Signed-off-by: Philipp Hahn <phahn-oss@avm.de>
---
security/integrity/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/integrity/Kconfig b/security/integrity/Kconfig
index 916d4f2bfc441..328ea9f32035a 100644
--- a/security/integrity/Kconfig
+++ b/security/integrity/Kconfig
@@ -60,7 +60,7 @@ config INTEGRITY_PLATFORM_KEYRING
help
Provide a separate, distinct keyring for platform trusted keys, which
the kernel automatically populates during initialization from values
- provided by the platform for verifying the kexec'ed kerned image
+ provided by the platform for verifying the kexec'ed kernel image
and, possibly, the initramfs signature.
config INTEGRITY_MACHINE_KEYRING
--
2.43.0
next reply other threads:[~2025-12-18 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 10:31 Philipp Hahn [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-12 9:35 [PATCH] integrity: Fix spelling mistake TRUSTED_KEYRING Philipp Hahn
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=4f736ebcd8a80c2e48c274cec027831d2986f792.1766053742.git.p.hahn@avm.de \
--to=phahn-oss@avm.de \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nayna@linux.ibm.com \
--cc=zohar@linux.ibm.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