From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][Doc] Fix kerneldoc comments in kernel/timer.c
Date: Sun, 6 Aug 2006 13:37:29 -0700 [thread overview]
Message-ID: <20060806133729.b389f1be.rdunlap@xenotime.net> (raw)
In-Reply-To: <200608011631.40189.eike-kernel@sf-tec.de>
On Tue, 1 Aug 2006 16:31:39 +0200 Rolf Eike Beer wrote:
> Some of the kerneldoc comments in this file are ignored since the lead-in is
> malformed, using either "/*" or "/***" instead of "/**".
>
> Signed-off-by: Rolf Eike Beer <eike-kernel@sf-tec.de>
> @@ -401,7 +405,7 @@ static int cascade(tvec_base_t *base, tv
> return index;
> }
>
> -/***
> +/**
> * __run_timers - run all expired timers (if any) on this CPU.
> * @base: the timer vector to be processed.
> *
Thanks for the patch, Eike. I noticed that __run_timers needs
some help. Patch below.
---
From: Randy Dunlap <rdunlap@xenotime.net>
Fix function description + definition so that a #macro does
not come between them and interfere with the kernel-doc.
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
kernel/timer.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--- linux-2618-rc3g2.orig/kernel/timer.c
+++ linux-2618-rc3g2/kernel/timer.c
@@ -405,6 +405,8 @@ static int cascade(tvec_base_t *base, tv
return index;
}
+#define INDEX(N) ((base->timer_jiffies >> (TVR_BITS + (N) * TVN_BITS)) & TVN_MASK)
+
/**
* __run_timers - run all expired timers (if any) on this CPU.
* @base: the timer vector to be processed.
@@ -412,8 +414,6 @@ static int cascade(tvec_base_t *base, tv
* This function cascades all vectors and executes all expired timer
* vectors.
*/
-#define INDEX(N) ((base->timer_jiffies >> (TVR_BITS + (N) * TVN_BITS)) & TVN_MASK)
-
static inline void __run_timers(tvec_base_t *base)
{
struct timer_list *timer;
prev parent reply other threads:[~2006-08-06 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 14:31 Rolf Eike Beer
2006-08-01 15:00 ` Alan Cox
2006-08-06 20:37 ` Randy.Dunlap [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=20060806133729.b389f1be.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=eike-kernel@sf-tec.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®