From: Jarkko Sakkinen <jarkko@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
corbet@lwn.net, mchehab+huawei@kernel.org,
linux-doc@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] watch_queue: rectify kernel-doc for init_watch()
Date: Fri, 19 Feb 2021 19:47:14 +0200 [thread overview]
Message-ID: <YC/5ojC2fwkY5Y9T@kernel.org> (raw)
In-Reply-To: <161373161298.2157082.10755433120775444271.stgit@warthog.procyon.org.uk>
On Fri, Feb 19, 2021 at 10:46:53AM +0000, David Howells wrote:
> From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>
> The command './scripts/kernel-doc -none kernel/watch_queue.c'
> reported a mismatch in the kernel-doc of init_watch().
>
> Rectify the kernel-doc, such that no issues remain for watch_queue.c.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> Signed-off-by: David Howells <dhowells@redhat.com>
> Link: https://lore.kernel.org/lkml/20210125161409.8478-1-lukas.bulwahn@gmail.com
> ---
>
> kernel/watch_queue.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/watch_queue.c b/kernel/watch_queue.c
> index 0ef8f65bd2d7..9c9eb20dd2c5 100644
> --- a/kernel/watch_queue.c
> +++ b/kernel/watch_queue.c
> @@ -413,7 +413,7 @@ static void put_watch(struct watch *watch)
> }
>
> /**
> - * init_watch_queue - Initialise a watch
> + * init_watch - Initialise a watch
> * @watch: The watch to initialise.
> * @wqueue: The queue to assign.
> *
>
>
>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
/Jarkko
next prev parent reply other threads:[~2021-02-19 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 10:46 [PATCH] watch_queue: rectify kernel-doc for init_watch() David Howells
2021-02-19 17:47 ` Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-25 16:14 Lukas Bulwahn
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=YC/5ojC2fwkY5Y9T@kernel.org \
--to=jarkko@kernel.org \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mchehab+huawei@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;
as well as URLs for NNTP newsgroup(s).