All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH 1/1] null_blk: Fix the WARNING: modpost: missing MODULE_DESCRIPTION()
Date: Mon, 29 Apr 2024 21:48:28 +0200	[thread overview]
Message-ID: <f5efd37a-d154-4215-bb4a-5971bde6df57@linux.dev> (raw)
In-Reply-To: <b42557c1-5462-4e58-8aac-3b6ee9ce6566@nvidia.com>


在 2024/4/29 21:45, Chaitanya Kulkarni 写道:
> On 4/29/24 02:12, Zhu Yanjun wrote:
>> No functional changes intended.
>>
>> Fixes: f2298c0403b0 ("null_blk: multi queue aware block test driver")
>> Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
>> ---
>>    drivers/block/null_blk/main.c | 1 +
>>    1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/block/null_blk/main.c b/drivers/block/null_blk/main.c
>> index eed63f95e89d..aa084ae75e53 100644
>> --- a/drivers/block/null_blk/main.c
>> +++ b/drivers/block/null_blk/main.c
>> @@ -2121,4 +2121,5 @@ module_init(null_init);
>>    module_exit(null_exit);
>>    
>>    MODULE_AUTHOR("Jens Axboe <axboe@kernel.dk>");
>> +MODULE_DESCRIPTION("Null test block driver");
> why not :-
>
> "multi queue aware block test driver"

Thanks a lot. The above is from Kconfig.

Your suggestion is more fascinating. If everyone agrees, I will use yours.

>
>>    MODULE_LICENSE("GPL");
> irrespective of that, looks good.
>
> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

Thanks

Zhu Yanjun

>
> -ck
>
>
-- 
I only represent myself.
Zhu Yanjun or Yanjun.Zhu


      reply	other threads:[~2024-04-29 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29  9:12 [PATCH 1/1] null_blk: Fix the WARNING: modpost: missing MODULE_DESCRIPTION() Zhu Yanjun
2024-04-29 19:45 ` Chaitanya Kulkarni
2024-04-29 19:48   ` Zhu Yanjun [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=f5efd37a-d154-4215-bb4a-5971bde6df57@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=axboe@kernel.dk \
    --cc=chaitanyak@nvidia.com \
    --cc=linux-block@vger.kernel.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 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.