From: "Paul E. McKenney" <paulmck@kernel.org>
To: Hui Su <sh_def@163.com>
Cc: josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
joel@joelfernandes.org, corbet@lwn.net, rcu@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/rcu: update the api of call_rcu()
Date: Thu, 15 Oct 2020 10:38:16 -0700 [thread overview]
Message-ID: <20201015173816.GZ3249@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20201015141334.GA20723@rlk>
On Thu, Oct 15, 2020 at 10:13:34PM +0800, Hui Su wrote:
> update the api of call_rcu()
>
> Signed-off-by: Hui Su <sh_def@163.com>
Good point, the typedef is more compact. Queued, thank you!
Thanx, Paul
> ---
> Documentation/RCU/whatisRCU.rst | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/Documentation/RCU/whatisRCU.rst b/Documentation/RCU/whatisRCU.rst
> index c7f147b8034f..aa7d5ed20da5 100644
> --- a/Documentation/RCU/whatisRCU.rst
> +++ b/Documentation/RCU/whatisRCU.rst
> @@ -497,8 +497,7 @@ long -- there might be other high-priority work to be done.
> In such cases, one uses call_rcu() rather than synchronize_rcu().
> The call_rcu() API is as follows::
>
> - void call_rcu(struct rcu_head * head,
> - void (*func)(struct rcu_head *head));
> + void call_rcu(struct rcu_head *head, rcu_callback_t func);
>
> This function invokes func(head) after a grace period has elapsed.
> This invocation might happen from either softirq or process context,
> --
> 2.25.1
>
>
parent reply other threads:[~2020-10-15 17:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201015141334.GA20723@rlk>]
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=20201015173816.GZ3249@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sh_def@163.com \
/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).