From: Greg KH <greg@kroah.com>
To: john stultz <johnstul@us.ibm.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>, Dave Jones <davej@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
george anzinger <george@mvista.com>
Subject: Re: [PATCH] linux-2.5.40_timer-changes_A3 (3/3 - integration)
Date: Wed, 2 Oct 2002 23:59:00 -0700 [thread overview]
Message-ID: <20021003065900.GB18481@kroah.com> (raw)
In-Reply-To: <1033625554.28783.66.camel@cog>
On Wed, Oct 02, 2002 at 11:12:34PM -0700, john stultz wrote:
> Linus, All,
>
> This is the final part 3 of 3 of my timer-change patch. Part 3
> integrates the moved code (from part 2) into the new infrastructure
> (from part 1).
Minor, minor comments:
> diff -Nru a/arch/i386/kernel/timer_pit.c b/arch/i386/kernel/timer_pit.c
> --- a/arch/i386/kernel/timer_pit.c Wed Oct 2 22:38:24 2002
> +++ b/arch/i386/kernel/timer_pit.c Wed Oct 2 22:38:24 2002
> @@ -1,3 +1,41 @@
> +/*
> + * This code largely moved from arch/i386/kernel/time.c.
> + * See comments there for proper credits.
> + */
> +
> +#include <linux/spinlock.h>
> +#include <linux/module.h>
> +#include <linux/device.h>
> +#include <asm/timer.h>
> +#include <asm/io.h>
> +
> +/* fwd declarations */
These don't have to be forward declarations, do they?
And can they be static?
> +int init_pit(void);
> +void mark_offset_pit(void);
> +unsigned long get_offset_pit(void);
> +
> +/* tsc timer_opts struct */
> +struct timer_opts timer_pit = {
> + init: init_pit,
> + mark_offset: mark_offset_pit,
> + get_offset: get_offset_pit
> +};
> +
> +
> +extern spinlock_t i8259A_lock;
> +extern spinlock_t i8253_lock;
> +#include "do_timer.h"
Shouldn't these 3 lines be above the "/* fwd declarations */" line?
Same minor comments for timer_tsc.c
thanks,
greg k-h
next prev parent reply other threads:[~2002-10-03 6:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 6:09 [PATCH] linux-2.5.40_timer-changes_A3 (1/3 - infrastructure) john stultz
2002-10-03 6:11 ` [PATCH] linux-2.5.40_timer-changes_A3 (2/3 - bulk move) john stultz
2002-10-03 6:12 ` [PATCH] linux-2.5.40_timer-changes_A3 (3/3 - integration) john stultz
2002-10-03 6:59 ` Greg KH [this message]
2002-10-03 7:13 ` john stultz
2002-10-03 7:28 ` Greg KH
2002-10-03 7:33 ` john stultz
2002-10-03 6:13 ` [RFC][PATCH] linux-2.5.40_cyclone-timer_B2 john stultz
2002-10-03 16:28 ` [PATCH] linux-2.5.40_timer-changes_A3 (1/3 - infrastructure) Patrick Mochel
2002-10-03 17:48 ` john stultz
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=20021003065900.GB18481@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).