From: Rusty Russell <rusty@rustcorp.com.au>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] mutex: add to kernel-locking docbook
Date: Mon, 6 Sep 2010 18:58:33 +0930 [thread overview]
Message-ID: <201009061858.34619.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20100902154816.6cc2f9ad.randy.dunlap@oracle.com>
On Fri, 3 Sep 2010 08:18:16 am Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix kernel-doc notation in linux/mutex.h and kernel/mutex.c,
> then add these 2 files to the kernel-locking docbook as the
> Mutex API reference chapter.
>
> Add one API function to mutex-design.txt and correct a typo in
> that file.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
Acked-by: Rusty Russell <rusty@rustcorp.com.au>
Thanks!
Rusty.
prev parent reply other threads:[~2010-09-06 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 22:48 [PATCH] mutex: add to kernel-locking docbook Randy Dunlap
2010-09-03 7:13 ` [tip:core/urgent] mutex: Fix annotations to include it in " tip-bot for Randy Dunlap
2010-09-06 9:28 ` Rusty Russell [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=201009061858.34619.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=randy.dunlap@oracle.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