From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org, rob@landley.net, rdunlap@infradead.org
Subject: + docbook-add-futexes-to-kernel-locking-docbook.patch added to -mm tree
Date: Fri, 14 Jun 2013 14:39:13 -0700 [thread overview]
Message-ID: <51bb8d81.OhR22XVQ1/4Cy2ki%akpm@linux-foundation.org> (raw)
Subject: + docbook-add-futexes-to-kernel-locking-docbook.patch added to -mm tree
To: rdunlap@infradead.org,rob@landley.net
From: akpm@linux-foundation.org
Date: Fri, 14 Jun 2013 14:39:13 -0700
The patch titled
Subject: docbook: add futexes to kernel-locking docbook
has been added to the -mm tree. Its filename is
docbook-add-futexes-to-kernel-locking-docbook.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: Randy Dunlap <rdunlap@infradead.org>
Subject: docbook: add futexes to kernel-locking docbook
Add Fast User Mutexes (futexes) to kernel-locking docbook.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Rob Landley <rob@landley.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
Documentation/DocBook/kernel-locking.tmpl | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff -puN Documentation/DocBook/kernel-locking.tmpl~docbook-add-futexes-to-kernel-locking-docbook Documentation/DocBook/kernel-locking.tmpl
--- a/Documentation/DocBook/kernel-locking.tmpl~docbook-add-futexes-to-kernel-locking-docbook
+++ a/Documentation/DocBook/kernel-locking.tmpl
@@ -1955,12 +1955,17 @@ machines due to caching.
</sect1>
</chapter>
- <chapter id="apiref">
+ <chapter id="apiref-mutex">
<title>Mutex API reference</title>
!Iinclude/linux/mutex.h
!Ekernel/mutex.c
</chapter>
+ <chapter id="apiref-futex">
+ <title>Futex API reference</title>
+!Ikernel/futex.c
+ </chapter>
+
<chapter id="references">
<title>Further reading</title>
_
Patches currently in -mm which might be from rdunlap@infradead.org are
linux-next.patch
docbook-add-futexes-to-kernel-locking-docbook.patch
debugging-keep-track-of-page-owners-fix-2.patch
reply other threads:[~2013-06-14 21:39 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=51bb8d81.OhR22XVQ1/4Cy2ki%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rob@landley.net \
/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).