From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: NeilBrown <neilb@suse.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
trondmy@hammerspace.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] rculist: improve documentation for list_for_each_entry_from_rcu()
Date: Wed, 20 Jun 2018 08:33:07 -0700 [thread overview]
Message-ID: <20180620153306.GA18484@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180618170111.GB3593@linux.vnet.ibm.com>
On Mon, Jun 18, 2018 at 10:01:11AM -0700, Paul E. McKenney wrote:
> On Mon, Jun 18, 2018 at 02:22:40PM +1000, NeilBrown wrote:
> >
> > Unfortunately the patch for adding list_for_each_entry_from_rcu()
> > wasn't the final patch after all review. It is functionally
> > correct but the documentation was incomplete.
> >
> > This patch adds this missing documentation which includes an update to
> > the documentation for list_for_each_entry_continue_rcu() to match the
> > documentation for the new list_for_each_entry_from_rcu(), and adds
> > list_for_each_entry_from_rcu() and the already existing
> > hlist_for_each_entry_from_rcu() to section 7 of whatisRCU.txt.
> >
> > Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > Signed-off-by: NeilBrown <neilb@suse.com>
>
> Once I rebase my commits to v4.18-rc1, I will apply this, thank you!
>
> (If you were wanting something else to happen with this patch, please
> let me know.)
And hearing no objections, I have applied it.
Thanx, Paul
prev parent reply other threads:[~2018-06-20 15:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 13:39 [GIT PULL] Please pull NFS client changes for 4.18 Trond Myklebust
2018-06-12 17:42 ` Linus Torvalds
2018-06-12 18:06 ` Linus Torvalds
2018-06-12 18:08 ` Linus Torvalds
2018-06-12 22:01 ` NeilBrown
2018-06-13 1:04 ` Paul E. McKenney
2018-06-13 1:11 ` Linus Torvalds
2018-06-13 1:39 ` Paul E. McKenney
2018-06-13 1:42 ` NeilBrown
2018-06-13 10:06 ` Paul E. McKenney
2018-06-18 4:22 ` [PATCH] rculist: improve documentation for list_for_each_entry_from_rcu() NeilBrown
2018-06-18 17:01 ` Paul E. McKenney
2018-06-20 15:33 ` Paul E. McKenney [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=20180620153306.GA18484@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
--cc=torvalds@linux-foundation.org \
--cc=trondmy@hammerspace.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