From: Amol Grover <frextrite@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: madhuparnabhowmik04@gmail.com, linux-doc@vger.kernel.org,
corbet@lwn.net, linux-kernel@vger.kernel.org,
rcu@vger.kernel.org, joel@joelfernandes.org, mchehab@kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH] Documentation: RCU: whatisRCU: Updated full list of RCU API
Date: Tue, 12 Nov 2019 12:36:38 +0530 [thread overview]
Message-ID: <20191112070638.GA2561@workstation-kernel-dev> (raw)
In-Reply-To: <20191111213659.GP2865@paulmck-ThinkPad-P72>
On Mon, Nov 11, 2019 at 01:36:59PM -0800, Paul E. McKenney wrote:
> On Mon, Nov 11, 2019 at 11:41:22PM +0530, madhuparnabhowmik04@gmail.com wrote:
> > From: Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com>
> >
> > This patch updates the list of RCU API in whatisRCU.rst.
> >
> > Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com>
>
> Queued, thank you! Phong, Amol, could you please take a look at this?
Tested-by: Amol Grover <frextrite@gmail.com>
Thanks
Amol
>
> Thanx, Paul
>
> > ---
> > Documentation/RCU/whatisRCU.rst | 9 +++++++--
> > 1 file changed, 7 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/RCU/whatisRCU.rst b/Documentation/RCU/whatisRCU.rst
> > index 2f6f6ebbc8b0..c7f147b8034f 100644
> > --- a/Documentation/RCU/whatisRCU.rst
> > +++ b/Documentation/RCU/whatisRCU.rst
> > @@ -884,11 +884,14 @@ in docbook. Here is the list, by category.
> > RCU list traversal::
> >
> > list_entry_rcu
> > + list_entry_lockless
> > list_first_entry_rcu
> > list_next_rcu
> > list_for_each_entry_rcu
> > list_for_each_entry_continue_rcu
> > list_for_each_entry_from_rcu
> > + list_first_or_null_rcu
> > + list_next_or_null_rcu
> > hlist_first_rcu
> > hlist_next_rcu
> > hlist_pprev_rcu
> > @@ -902,7 +905,7 @@ RCU list traversal::
> > hlist_bl_first_rcu
> > hlist_bl_for_each_entry_rcu
> >
> > -RCU pointer/list udate::
> > +RCU pointer/list update::
> >
> > rcu_assign_pointer
> > list_add_rcu
> > @@ -912,10 +915,12 @@ RCU pointer/list udate::
> > hlist_add_behind_rcu
> > hlist_add_before_rcu
> > hlist_add_head_rcu
> > + hlist_add_tail_rcu
> > hlist_del_rcu
> > hlist_del_init_rcu
> > hlist_replace_rcu
> > - list_splice_init_rcu()
> > + list_splice_init_rcu
> > + list_splice_tail_init_rcu
> > hlist_nulls_del_init_rcu
> > hlist_nulls_del_rcu
> > hlist_nulls_add_head_rcu
> > --
> > 2.17.1
> >
> _______________________________________________
> Linux-kernel-mentees mailing list
> Linux-kernel-mentees@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2019-11-12 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 18:11 [PATCH] Documentation: RCU: whatisRCU: Updated full list of RCU API madhuparnabhowmik04
2019-11-11 21:36 ` Paul E. McKenney
2019-11-12 7:06 ` Amol Grover [this message]
2019-11-12 0:03 ` [Linux-kernel-mentees] " Phong Tran
2019-11-12 13:36 ` Paul E. McKenney
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=20191112070638.GA2561@workstation-kernel-dev \
--to=frextrite@gmail.com \
--cc=corbet@lwn.net \
--cc=joel@joelfernandes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik04@gmail.com \
--cc=mchehab@kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@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;
as well as URLs for NNTP newsgroup(s).