From: John Johansen <john.johansen@canonical.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Cc: apparmor@lists.ubuntu.com, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] apparmor: test: add MODULE_DESCRIPTION()
Date: Tue, 25 Jun 2024 01:26:04 -0700 [thread overview]
Message-ID: <17dad6b9-9dc3-4b0f-bd3d-34e9e22e7627@canonical.com> (raw)
In-Reply-To: <20240529-md-apparmor_policy_unpack_test-v1-1-9efc582078c4@quicinc.com>
On 5/29/24 18:21, Jeff Johnson wrote:
> Fix the 'make W=1' warning:
> WARNING: modpost: missing MODULE_DESCRIPTION() in security/apparmor/apparmor_policy_unpack_test.o
>
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
Acked-by: John Johansen <john.johansen@canonical.com>
I will pull this into my tree
> ---
> security/apparmor/policy_unpack_test.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/security/apparmor/policy_unpack_test.c b/security/apparmor/policy_unpack_test.c
> index 5c9bde25e56d..874fcf97794e 100644
> --- a/security/apparmor/policy_unpack_test.c
> +++ b/security/apparmor/policy_unpack_test.c
> @@ -604,4 +604,5 @@ static struct kunit_suite apparmor_policy_unpack_test_module = {
>
> kunit_test_suite(apparmor_policy_unpack_test_module);
>
> +MODULE_DESCRIPTION("KUnit tests for AppArmor's policy unpack");
> MODULE_LICENSE("GPL");
>
> ---
> base-commit: 4a4be1ad3a6efea16c56615f31117590fd881358
> change-id: 20240529-md-apparmor_policy_unpack_test-7657c4f11591
>
next prev parent reply other threads:[~2024-06-25 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 1:21 Jeff Johnson
2024-06-20 16:21 ` Jeff Johnson
2024-06-25 8:26 ` John Johansen
2024-06-25 8:26 ` John Johansen [this message]
2024-07-11 17:45 ` Jeff Johnson
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=17dad6b9-9dc3-4b0f-bd3d-34e9e22e7627@canonical.com \
--to=john.johansen@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=jmorris@namei.org \
--cc=kernel-janitors@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 \
/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®