From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: v9fs@lists.linux.dev, Dominique Martinet <asmadeus@codewreck.org>
Cc: ericvh@kernel.org, lucho@ionkov.net,
linux-kernel@vger.kernel.org,
Dominique Martinet <asmadeus@codewreck.org>
Subject: Re: [PATCH] 9p/fs: add MODULE_DESCIPTION
Date: Thu, 26 Oct 2023 14:47:33 +0200 [thread overview]
Message-ID: <2207070.NGFuZe4fYI@silver> (raw)
In-Reply-To: <20231025223107.1274963-1-asmadeus@codewreck.org>
On Thursday, October 26, 2023 12:31:07 AM CEST Dominique Martinet wrote:
> Fix modpost warning that MODULE_DESCRIPTION is missing in fs/9p/9p.o
>
> Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>
> ---
Reviewed-by: Christian Schoenebeck <linux_oss@crudebyte.com>
> Probably doesn't really matter after all this time, but noticed this
> when double-checking there weren't any warnings left in W=1... Might as
> well get rid of this:
> WARNING: modpost: missing MODULE_DESCRIPTION() in fs/9p/9p.o
>
> fs/9p/v9fs.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/9p/v9fs.c b/fs/9p/v9fs.c
> index d525957594b6..61dbe52bb3a3 100644
> --- a/fs/9p/v9fs.c
> +++ b/fs/9p/v9fs.c
> @@ -732,4 +732,5 @@ module_exit(exit_v9fs)
> MODULE_AUTHOR("Latchesar Ionkov <lucho@ionkov.net>");
> MODULE_AUTHOR("Eric Van Hensbergen <ericvh@gmail.com>");
> MODULE_AUTHOR("Ron Minnich <rminnich@lanl.gov>");
> +MODULE_DESCRIPTION("9P Client File System");
> MODULE_LICENSE("GPL");
>
prev parent reply other threads:[~2023-10-26 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 22:31 [PATCH] 9p/fs: add MODULE_DESCIPTION Dominique Martinet
2023-10-26 12:47 ` Christian Schoenebeck [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=2207070.NGFuZe4fYI@silver \
--to=linux_oss@crudebyte.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=v9fs@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).