From: Waiman Long <longman@redhat.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 5/5] locking/ww_mutex/test: add MODULE_DESCRIPTION()
Date: Tue, 30 Jul 2024 14:50:45 -0000 [thread overview]
Message-ID: <5ecb4ac2-6204-4c20-b98d-9a0e1b33c5f0@redhat.com> (raw)
In-Reply-To: <20240730-module_description_orphans-v1-5-7094088076c8@quicinc.com>
On 7/30/24 10:43, Jeff Johnson wrote:
> Fix the 'make W=1' warning:
> WARNING: modpost: missing MODULE_DESCRIPTION() in kernel/locking/test-ww_mutex.o
>
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> ---
> kernel/locking/test-ww_mutex.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/locking/test-ww_mutex.c b/kernel/locking/test-ww_mutex.c
> index 78719e1ef1b1..10a5736a21c2 100644
> --- a/kernel/locking/test-ww_mutex.c
> +++ b/kernel/locking/test-ww_mutex.c
> @@ -697,3 +697,4 @@ module_exit(test_ww_mutex_exit);
>
> MODULE_LICENSE("GPL");
> MODULE_AUTHOR("Intel Corporation");
> +MODULE_DESCRIPTION("API test facility for ww_mutexes");
Acked-by: Waiman Long <longman@redhat.com>
next prev parent reply other threads:[~2024-07-30 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 14:44 [PATCH 0/5] treewide: add missing MODULE_DESCRIPTION() macros Jeff Johnson
2024-07-30 14:44 ` [PATCH 4/5] fsi: " Jeff Johnson
2024-07-30 14:44 ` [PATCH 1/5] crypto: arm/xor - add missing MODULE_DESCRIPTION() macro Jeff Johnson
2024-07-30 14:44 ` [PATCH 2/5] x86/mm: add testmmiotrace MODULE_DESCRIPTION() Jeff Johnson
2024-07-30 14:44 ` [PATCH 5/5] locking/ww_mutex/test: add MODULE_DESCRIPTION() Jeff Johnson
2024-07-30 14:50 ` Waiman Long [this message]
2024-07-30 14:45 ` [PATCH 3/5] cpufreq: powerpc: add missing MODULE_DESCRIPTION() macros 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=5ecb4ac2-6204-4c20-b98d-9a0e1b33c5f0@redhat.com \
--to=longman@redhat.com \
--cc=linux-aspeed@lists.ozlabs.org \
/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