From: Ingo Molnar <mingo@elte.hu>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, mingo <mingo@redhat.com>,
akpm <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] sched: add missing kernel-doc in sched.h
Date: Tue, 3 Feb 2009 06:32:24 +0100 [thread overview]
Message-ID: <20090203053224.GE28361@elte.hu> (raw)
In-Reply-To: <20090202160029.dfea8898.randy.dunlap@oracle.com>
* Randy Dunlap <randy.dunlap@oracle.com> wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Add kernel-doc notation for @lock:
>
> include/linux/sched.h:457: No description found for parameter 'lock'
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
> include/linux/sched.h | 1 +
> 1 file changed, 1 insertion(+)
Applied to tip/sched/urgent, thanks Randy!
Ingo
prev parent reply other threads:[~2009-02-03 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 0:00 [PATCH] sched: add missing kernel-doc in sched.h Randy Dunlap
2009-02-03 5:32 ` Ingo Molnar [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=20090203053224.GE28361@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--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