From: Marco Elver <elver@google.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kasan-dev@googlegroups.com
Subject: Re: [PATCH 3/4] mm/kfence: add MODULE_DESCRIPTION()
Date: Mon, 13 May 2024 21:42:55 +0200 [thread overview]
Message-ID: <CANpmjNOAJOsa3S5K2kdMQo+rS8WJpsT3Rew96VMfmftC_naRNQ@mail.gmail.com> (raw)
In-Reply-To: <20240513-mm-md-v1-3-8c20e7d26842@quicinc.com>
On Mon, 13 May 2024 at 21:38, Jeff Johnson <quic_jjohnson@quicinc.com> wrote:
>
> Fix the 'make W=1' warning:
>
> WARNING: modpost: missing MODULE_DESCRIPTION() in mm/kfence/kfence_test.o
>
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> ---
> mm/kfence/kfence_test.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/kfence/kfence_test.c b/mm/kfence/kfence_test.c
> index 95b2b84c296d..00fd17285285 100644
> --- a/mm/kfence/kfence_test.c
> +++ b/mm/kfence/kfence_test.c
> @@ -852,3 +852,4 @@ kunit_test_suites(&kfence_test_suite);
>
> MODULE_LICENSE("GPL v2");
> MODULE_AUTHOR("Alexander Potapenko <glider@google.com>, Marco Elver <elver@google.com>");
> +MODULE_DESCRIPTION("kfence unit test suite");
Reviewed-by: Marco Elver <elver@google.com>
I guess this warning has been there since the beginning, we just never
compiled this module with W=1.
Thanks,
-- Marco
next prev parent reply other threads:[~2024-05-13 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 19:37 [PATCH 0/4] mm: add missing MODULE_DESCRIPTION() macros Jeff Johnson
2024-05-13 19:37 ` [PATCH 1/4] mm/hwpoison: add MODULE_DESCRIPTION() Jeff Johnson
2024-05-14 3:14 ` Miaohe Lin
2024-05-13 19:37 ` [PATCH 2/4] mm/dmapool: " Jeff Johnson
2024-05-13 19:37 ` [PATCH 3/4] mm/kfence: " Jeff Johnson
2024-05-13 19:42 ` Marco Elver [this message]
2024-05-13 19:37 ` [PATCH 4/4] mm/zsmalloc: " Jeff Johnson
2024-05-14 0:41 ` Sergey Senozhatsky
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=CANpmjNOAJOsa3S5K2kdMQo+rS8WJpsT3Rew96VMfmftC_naRNQ@mail.gmail.com \
--to=elver@google.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nao.horiguchi@gmail.com \
--cc=quic_jjohnson@quicinc.com \
--cc=senozhatsky@chromium.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;
as well as URLs for NNTP newsgroup(s).