mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] lib/test_linear_ranges: add missing MODULE_DESCRIPTION() macro
Date: Mon, 3 Jun 2024 08:17:15 +0300	[thread overview]
Message-ID: <9db9583a-4552-474d-bec1-f2fd1e486c9e@gmail.com> (raw)
In-Reply-To: <20240531-md-lib-test_linear_ranges-v1-1-053a1aad37c6@quicinc.com>

On 6/1/24 02:45, Jeff Johnson wrote:
> make allmodconfig && make W=1 C=1 reports:
> WARNING: modpost: missing MODULE_DESCRIPTION() in lib/test_linear_ranges.o
> 
> Add the missing invocation of the MODULE_DESCRIPTION() macro.
> 
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>

Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>

Thanks!

> ---
>   lib/test_linear_ranges.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/lib/test_linear_ranges.c b/lib/test_linear_ranges.c
> index c18f9c0f1f25..f482be00f1bc 100644
> --- a/lib/test_linear_ranges.c
> +++ b/lib/test_linear_ranges.c
> @@ -216,4 +216,5 @@ static struct kunit_suite range_test_module = {
>   
>   kunit_test_suites(&range_test_module);
>   
> +MODULE_DESCRIPTION("KUnit test for the linear_ranges helper");
>   MODULE_LICENSE("GPL");
> 
> ---
> base-commit: b050496579632f86ee1ef7e7501906db579f3457
> change-id: 20240531-md-lib-test_linear_ranges-6807dcb18e7e
> 

-- 
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland

~~ When things go utterly wrong vim users can always type :help! ~~


      reply	other threads:[~2024-06-03  5:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 23:45 Jeff Johnson
2024-06-03  5:17 ` Matti Vaittinen [this message]

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=9db9583a-4552-474d-bec1-f2fd1e486c9e@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_jjohnson@quicinc.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®