From: Jonathan Corbet <corbet@lwn.net>
To: Andreas-Christian Hagau <ach@hagau.se>,
Brendan Higgins <brendanhiggins@google.com>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: kunit: change complete_and_exit to kthread_complete_and_exit
Date: Wed, 20 Apr 2022 03:32:26 -0600 [thread overview]
Message-ID: <877d7k3xsl.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220417102807.10b91497ed@19d04f311a0a9de>
Andreas-Christian Hagau <ach@hagau.se> writes:
> Commit cead18552660 ("exit: Rename complete_and_exit to
> kthread_complete_and_exit") renamed complete_and_exit to
> kthread_complete_and_exit.
>
> Signed-off-by: Andreas-Christian Hagau <ach@hagau.se>
> ---
> Documentation/dev-tools/kunit/architecture.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/dev-tools/kunit/architecture.rst b/Documentation/dev-tools/kunit/architecture.rst
> index ff9c85a0bff21..cf9e6e3eeae4c 100644
> --- a/Documentation/dev-tools/kunit/architecture.rst
> +++ b/Documentation/dev-tools/kunit/architecture.rst
> @@ -125,7 +125,7 @@ All expectations/assertions are formatted as:
> ``void __noreturn kunit_try_catch_throw(struct kunit_try_catch *try_catch)``.
>
> - ``kunit_try_catch_throw`` calls function:
> - ``void complete_and_exit(struct completion *, long) __noreturn;``
> + ``void kthread_complete_and_exit(struct completion *, long) __noreturn;``
> and terminates the special thread context.
Applied, thanks.
jon
prev parent reply other threads:[~2022-04-20 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 8:37 Andreas-Christian Hagau
2022-04-18 21:29 ` Brendan Higgins
2022-04-20 9:32 ` Jonathan Corbet [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=877d7k3xsl.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=ach@hagau.se \
--cc=brendanhiggins@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@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
Powered by JetHome