linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Mimi Zohar <zohar@linux.ibm.com>,
	 David Howells <dhowells@redhat.com>,
	James Morris <jmorris@namei.org>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	 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
Subject: Re: [PATCH v3 1/2] KEYS: trusted: add missing MODULE_DESCRIPTION()
Date: Mon, 01 Jul 2024 15:00:28 +0000	[thread overview]
Message-ID: <4258218f9de3a70e7a04783881baed3879a914f1.camel@kernel.org> (raw)
In-Reply-To: <CAHC9VhSVSS46oCAz_NrUUGstmG3j0NVk70-SwwtCTVJ-R1Z+OA@mail.gmail.com>

On Thu, 2024-06-20 at 12:54 -0400, Paul Moore wrote:
> On Wed, Jun 19, 2024 at 8:19 PM Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > On Fri Jun 7, 2024 at 4:47 AM EEST, Jeff Johnson wrote:
> > > kbuild reports:
> > > 
> > > WARNING: modpost: missing MODULE_DESCRIPTION() in security/keys/trusted-keys/trusted.o
> > > 
> > > Add the missing MODULE_DESCRIPTION() macro invocation.
> > > 
> > > Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> > > ---
> > >  security/keys/trusted-keys/trusted_core.c | 1 +
> > >  1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/security/keys/trusted-keys/trusted_core.c b/security/keys/trusted-
> > > keys/trusted_core.c
> > > index 5113aeae5628..e2d9644efde1 100644
> > > --- a/security/keys/trusted-keys/trusted_core.c
> > > +++ b/security/keys/trusted-keys/trusted_core.c
> > > @@ -395,4 +395,5 @@ static void __exit cleanup_trusted(void)
> > >  late_initcall(init_trusted);
> > >  module_exit(cleanup_trusted);
> > > 
> > > +MODULE_DESCRIPTION("Trusted Key type");
> > >  MODULE_LICENSE("GPL");
> > 
> > Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> 
> Are you planning on taking these patches Jarkko?

Hi, both are now applied.

Except slow phase this month as I'm on holiday. I'll take care of
v6.11 PR's.

BR, Jarkko

  reply	other threads:[~2024-07-01 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  1:47 [PATCH v3 0/2] KEYS: add missing MODULE_DESCRIPTION() macros Jeff Johnson
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 [this message]
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=4258218f9de3a70e7a04783881baed3879a914f1.camel@kernel.org \
    --to=jarkko@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dhowells@redhat.com \
    --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=quic_jjohnson@quicinc.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).