From: akpm@linux-foundation.org
To: aurorean@gmail.com, mm-commits@vger.kernel.org
Subject: + lib-radix_tree-fix-error-in-docs-about-locks.patch added to -mm tree
Date: Mon, 21 Dec 2015 15:13:11 -0800 [thread overview]
Message-ID: <56788787.UUA90vVBM7djvnpS%akpm@linux-foundation.org> (raw)
The patch titled
Subject: include/linux/radix-tree.h: fix error in docs about locks
has been added to the -mm tree. Its filename is
lib-radix_tree-fix-error-in-docs-about-locks.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/lib-radix_tree-fix-error-in-docs-about-locks.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/lib-radix_tree-fix-error-in-docs-about-locks.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Adam Barth <aurorean@gmail.com>
Subject: include/linux/radix-tree.h: fix error in docs about locks
This text refers to the "first 7 functions", which was correct when
written but became incorrect when Johannes Weiner added another function
to the list in 139e561660fe ("lib: radix_tree: tree node interface").
Change the text to correctly refer to the first 8 functions.
Signed-off-by: Adam Barth <aurorean@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/radix-tree.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN include/linux/radix-tree.h~lib-radix_tree-fix-error-in-docs-about-locks include/linux/radix-tree.h
--- a/include/linux/radix-tree.h~lib-radix_tree-fix-error-in-docs-about-locks
+++ a/include/linux/radix-tree.h
@@ -154,7 +154,7 @@ do { \
* radix_tree_gang_lookup_tag_slot
* radix_tree_tagged
*
- * The first 7 functions are able to be called locklessly, using RCU. The
+ * The first 8 functions are able to be called locklessly, using RCU. The
* caller must ensure calls to these functions are made within rcu_read_lock()
* regions. Other readers (lock-free or otherwise) and modifications may be
* running concurrently.
_
Patches currently in -mm which might be from aurorean@gmail.com are
lib-radix_tree-fix-error-in-docs-about-locks.patch
reply other threads:[~2015-12-21 23:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56788787.UUA90vVBM7djvnpS%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aurorean@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.