From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>, "Jens Axboe" <axboe@kernel.dk>
Cc: <xen-devel@lists.xenproject.org>, <linux-block@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] xen/blkback: add missing MODULE_DESCRIPTION() macro
Date: Tue, 9 Jul 2024 13:01:12 -0700 [thread overview]
Message-ID: <42b70860-e06f-40b7-9bda-6a512ed1dd9d@quicinc.com> (raw)
In-Reply-To: <20240602-md-block-xen-blkback-v1-1-6ff5b58bdee1@quicinc.com>
On 6/2/2024 5:37 PM, Jeff Johnson wrote:
> make allmodconfig && make W=1 C=1 reports:
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/block/xen-blkback/xen-blkback.o
>
> Add the missing invocation of the MODULE_DESCRIPTION() macro.
>
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> ---
> drivers/block/xen-blkback/blkback.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/block/xen-blkback/blkback.c b/drivers/block/xen-blkback/blkback.c
> index 944576d582fb..838064593f62 100644
> --- a/drivers/block/xen-blkback/blkback.c
> +++ b/drivers/block/xen-blkback/blkback.c
> @@ -1563,5 +1563,6 @@ static void __exit xen_blkif_fini(void)
>
> module_exit(xen_blkif_fini);
>
> +MODULE_DESCRIPTION("Virtual block device back-end driver");
> MODULE_LICENSE("Dual BSD/GPL");
> MODULE_ALIAS("xen-backend:vbd");
>
> ---
> base-commit: a693b9c95abd4947c2d06e05733de5d470ab6586
> change-id: 20240602-md-block-xen-blkback-0db494d277af
I don't see this in linux-next yet so following up to see if anything else is
needed to get this merged.
next prev parent reply other threads:[~2024-07-09 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 0:37 Jeff Johnson
2024-07-09 20:01 ` Jeff Johnson [this message]
2024-07-10 6:23 ` Jens Axboe
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=42b70860-e06f-40b7-9bda-6a512ed1dd9d@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=axboe@kernel.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®