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>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] futex: fix kernel-doc notation & typos
Date: Thu, 14 Oct 2010 11:44:32 +1030 [thread overview]
Message-ID: <201010141144.32470.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20101013110234.89b06043.randy.dunlap@oracle.com>
On Thu, 14 Oct 2010 04:32:34 am Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Convert futex_requeue() function parameters to use @name kernel-doc
> notation and add @fshared & @cmpval to prevent kernel-doc warnings.
>
> Add @list to struct futex_q.
>
> Fix a few typos.
Thanks,
Acked-by: Rusty Russell <rusty@rustcorp.com.au>
Isn't this a job for the trivial patch monkey?
Rusty.
next prev parent reply other threads:[~2010-10-14 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 18:02 [PATCH] futex: fix kernel-doc notation & typos Randy Dunlap
2010-10-14 1:14 ` Rusty Russell [this message]
2010-10-14 7:41 ` [tip:core/futexes] futex: Fix " tip-bot for Randy Dunlap
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=201010141144.32470.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=randy.dunlap@oracle.com \
--cc=tglx@linutronix.de \
/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