From: Joel Fernandes <joel@joelfernandes.org> To: madhuparnabhowmik04@gmail.com Cc: paulmck@kernel.org, rcu@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kernel-mentees@lists.linuxfoundation.org Subject: Re: [PATCH] Include: Linux: rculist_nulls: Add docbook comment headers Date: Wed, 4 Dec 2019 12:44:47 -0500 Message-ID: <20191204174447.GE34402@google.com> (raw) In-Reply-To: <20191204120357.11658-1-madhuparnabhowmik04@gmail.com> On Wed, Dec 04, 2019 at 05:33:57PM +0530, madhuparnabhowmik04@gmail.com wrote: > From: Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com> > > This patch adds docbook comment headers for hlist_nulls_first_rcu > and hlist_nulls_next_rcu in rculist_nulls.h. > > Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com> Thanks. Could you send this to the list? I'd like Paul to review or apply this one. - Joel > --- > include/linux/rculist_nulls.h | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/include/linux/rculist_nulls.h b/include/linux/rculist_nulls.h > index 517a06f36c7a..d796ef18ec52 100644 > --- a/include/linux/rculist_nulls.h > +++ b/include/linux/rculist_nulls.h > @@ -38,9 +38,17 @@ static inline void hlist_nulls_del_init_rcu(struct hlist_nulls_node *n) > } > } > > +/** > + * hlist_nulls_first_rcu - returns the first element of the hash list. > + * @head: the head for your list. > + */ > #define hlist_nulls_first_rcu(head) \ > (*((struct hlist_nulls_node __rcu __force **)&(head)->first)) > > +/** > + * hlist_nulls_next_rcu - returns the element of the list next to @node. > + * @node: Element of the list. > + */ > #define hlist_nulls_next_rcu(node) \ > (*((struct hlist_nulls_node __rcu __force **)&(node)->next)) > > -- > 2.17.1 >
next prev parent reply index Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-04 12:03 madhuparnabhowmik04 2019-12-04 17:44 ` Joel Fernandes [this message] 2019-12-05 0:25 ` Paul E. McKenney [not found] ` <CAF65HP1WL2yw8nVZi-j9=eehkUJP-eKUy+w9unFXddmPf7_Hqg@mail.gmail.com> 2019-12-05 14:42 ` Paul E. McKenney
Reply instructions: You may reply publically 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=20191204174447.GE34402@google.com \ --to=joel@joelfernandes.org \ --cc=linux-kernel-mentees@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=madhuparnabhowmik04@gmail.com \ --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
RCU Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/rcu/0 rcu/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 rcu rcu/ https://lore.kernel.org/rcu \ rcu@vger.kernel.org public-inbox-index rcu Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.rcu AGPL code for this site: git clone https://public-inbox.org/public-inbox.git