From: Damien Le Moal <dlemoal@kernel.org>
To: Chaitanya Kulkarni <kch@nvidia.com>, linux-block@vger.kernel.org
Cc: axboe@kernel.dk, hch@lst.de
Subject: Re: [PATCH] block: fix get_max_segment_size() warning
Date: Tue, 9 Jul 2024 14:44:22 +0900 [thread overview]
Message-ID: <9d58d0ad-4afc-4cd8-ae2d-96bf8708a14c@kernel.org> (raw)
In-Reply-To: <20240709045432.8688-1-kch@nvidia.com>
On 7/9/24 13:54, Chaitanya Kulkarni wrote:
> Correct the parameter name in the comment of get_max_segment_size()
> to fix following warning:-
>
> block/blk-merge.c:220: warning: Function parameter or struct member 'len' not described in 'get_max_segment_size'
> block/blk-merge.c:220: warning: Excess function parameter 'max_len' description in 'get_max_segment_size'
>
> Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-07-09 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 4:54 [PATCH] block: fix get_max_segment_size() warning Chaitanya Kulkarni
2024-07-09 5:44 ` Damien Le Moal [this message]
2024-07-09 6:01 ` Jens Axboe
2024-07-09 6:20 ` Christoph Hellwig
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=9d58d0ad-4afc-4cd8-ae2d-96bf8708a14c@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox