From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Mimi Zohar <zohar@linux.ibm.com>,
David Howells <dhowells@redhat.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Cc: <linux-integrity@vger.kernel.org>, <keyrings@vger.kernel.org>,
<linux-security-module@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: [PATCH v3 0/2] KEYS: add missing MODULE_DESCRIPTION() macros
Date: Thu, 6 Jun 2024 18:47:05 -0700 [thread overview]
Message-ID: <20240606-md-trusted-v3-0-42716f15e66e@quicinc.com> (raw)
---
Changes in v3:
- Per Jarkko's feedback, this is now a series since a 2nd patch was
added to address the missing MODULE_DESCRIPTION() in the
encrypted-keys module (even though this is currently built-in, even
with an allmodconfig, at least for x86)
- Also per Jarkko's feedback, the MODULE_DESCRIPTION() in the trusted
module was updated.
- Link to v2: https://lore.kernel.org/r/20240530-md-trusted-v2-1-151f0c7be272@quicinc.com
Changes in v2:
- reword commit text per Jarkko's guidance
- Link to v1: https://lore.kernel.org/r/20240529-md-trusted-v1-1-56c9a0ae8e28@quicinc.com
---
Jeff Johnson (2):
KEYS: trusted: add missing MODULE_DESCRIPTION()
KEYS: encrypted: add missing MODULE_DESCRIPTION()
security/keys/encrypted-keys/encrypted.c | 1 +
security/keys/trusted-keys/trusted_core.c | 1 +
2 files changed, 2 insertions(+)
---
base-commit: 4a4be1ad3a6efea16c56615f31117590fd881358
change-id: 20240529-md-trusted-6e6fd26299ad
next reply other threads:[~2024-06-07 1:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 1:47 Jeff Johnson [this message]
2024-06-07 1:47 ` [PATCH v3 1/2] KEYS: trusted: add missing MODULE_DESCRIPTION() Jeff Johnson
2024-06-20 0:19 ` Jarkko Sakkinen
2024-06-20 16:54 ` Paul Moore
2024-07-01 15:00 ` Jarkko Sakkinen
2024-06-07 1:47 ` [PATCH v3 2/2] KEYS: encrypted: " Jeff Johnson
2024-06-20 0:19 ` Jarkko Sakkinen
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=20240606-md-trusted-v3-0-42716f15e66e@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).