From: Saket Kumar Bhaskar <skb99@linux.ibm.com>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Cc: sfrench@samba.org, pc@manguebit.org, maddy@linux.ibm.com,
linux-cifs@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] smb: client: add missing MODULE_DESCRIPTION() to smb1maperror_test
Date: Fri, 10 Apr 2026 14:01:00 +0530 [thread overview]
Message-ID: <adi1RHPWcz-zsYUP@linux.ibm.com> (raw)
In-Reply-To: <20260410064030.89137-1-venkat88@linux.ibm.com>
On Fri, Apr 10, 2026 at 12:10:30PM +0530, Venkat Rao Bagalkote wrote:
> On the latest linux-next following modpost warning is reported:
>
> WARNING: modpost: missing MODULE_DESCRIPTION() in
> fs/smb/client/smb1maperror_test.o
>
> Add MODULE_DESCRIPTION() to the test module to fix the warning.
>
> Signed-off-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
> ---
> Changes in v2:
> - Fix typo in MODULE_DESCRIPTION
>
> fs/smb/client/smb1maperror_test.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/smb/client/smb1maperror_test.c b/fs/smb/client/smb1maperror_test.c
> index 820c0dd3bcce..b93d3ac41f91 100644
> --- a/fs/smb/client/smb1maperror_test.c
> +++ b/fs/smb/client/smb1maperror_test.c
> @@ -74,3 +74,4 @@ static struct kunit_suite maperror_suite = {
> kunit_test_suite(maperror_suite);
>
> MODULE_LICENSE("GPL");
> +MODULE_DESCRIPTION("SMB1 error mapping selftest module");
> --
> 2.45.2
>
LGTM, feel free to add below tag:
Reviewed-by: Saket Kumar Bhaskar <skb99@linux.ibm.com>
next prev parent reply other threads:[~2026-04-10 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 6:40 [PATCH v2] smb: client: add missing MODULE_DESCRIPTION() to smb1maperror_test Venkat Rao Bagalkote
2026-04-10 8:31 ` Saket Kumar Bhaskar [this message]
2026-04-10 13:52 ` ChenXiaoSong
2026-04-10 15:11 ` Venkat Rao Bagalkote
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=adi1RHPWcz-zsYUP@linux.ibm.com \
--to=skb99@linux.ibm.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=pc@manguebit.org \
--cc=sfrench@samba.org \
--cc=venkat88@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.