From: Randy Dunlap <rdunlap@infradead.org>
To: Masanari Iida <standby24x7@gmail.com>,
viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, tj@kernel.org, axboe@kernel.dk
Subject: Re: [PATCH] writeback: Fix a warning while "make xmldocs"
Date: Sat, 12 Oct 2019 23:17:18 -0700 [thread overview]
Message-ID: <fcb2c42a-9ee9-7f59-0543-eca6e188ac00@infradead.org> (raw)
In-Reply-To: <20191013040837.14766-1-standby24x7@gmail.com>
On 10/12/19 9:08 PM, Masanari Iida wrote:
> This patch fix following warning.
> ./fs/fs-writeback.c:918: warning: Excess function parameter
> 'nr_pages' description in 'cgroup_writeback_by_id'
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
> fs/fs-writeback.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index e88421d9a48d..8461a6322039 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -905,7 +905,7 @@ static void bdi_split_work_to_wbs(struct backing_dev_info *bdi,
> * cgroup_writeback_by_id - initiate cgroup writeback from bdi and memcg IDs
> * @bdi_id: target bdi id
> * @memcg_id: target memcg css id
> - * @nr_pages: number of pages to write, 0 for best-effort dirty flushing
> + * @nr: number of pages to write, 0 for best-effort dirty flushing
> * @reason: reason why some writeback work initiated
> * @done: target wb_completion
> *
>
https://lore.kernel.org/linux-fsdevel/756645ac-0ce8-d47e-d30a-04d9e4923a4f@infradead.org/
Andrew has already added this to his patches.
--
~Randy
prev parent reply other threads:[~2019-10-13 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 4:08 [PATCH] writeback: Fix a warning while "make xmldocs" Masanari Iida
2019-10-13 6:17 ` Randy Dunlap [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=fcb2c42a-9ee9-7f59-0543-eca6e188ac00@infradead.org \
--to=rdunlap@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=standby24x7@gmail.com \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).