All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	parisc-linux@parisc-linux.org,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: [parisc-linux] Re: Generic RTC driver in 2.4.x
Date: Sun, 12 Jan 2003 13:35:33 +0100	[thread overview]
Message-ID: <200301121333.17077.deller@gmx.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0301121214440.18673-100000@vervain.sonytel.be>

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

On Sunday 12 January 2003 12:33, Geert Uytterhoeven wrote:
> I made some more changes afterwards:
>   - Add forward declaration for gen_rtc_interrupt()

This one should be moved inside the #ifdef CONFIG_GEN_RTC_X section to
avoid "genrtc.c:69: warning: `gen_rtc_interrupt' declared `static' but never defined"
warnings. Please see attached patch.

Or, you could just move the declaration of gen_rtc_interrupt() above the one
from genrtc_troutine(), in which case we wouldn't need the forward declaration at all.

> BTW, perhaps we should move the global RTC_* definitions in <asm/rtc.h> to
> <linux/genrtc.h>, or merge them with the ones in <linux/mc146818rtc.h> and
> move them to <linux/rtc.h>?

IMHO leaving them architecture specific in <asm/rtc.h> seems best to me, and it 
leaves the most possibilities to make them later more dependend on the hardware.

Helge


[-- Attachment #2: diff --]
[-- Type: text/plain, Size: 574 bytes --]

--- ./genrtc.c.geert	Sun Jan 12 13:16:40 2003
+++ ./genrtc.c	Sun Jan 12 13:15:18 2003
@@ -66,9 +66,6 @@
 
 static DECLARE_WAIT_QUEUE_HEAD(gen_rtc_wait);
 
-static void gen_rtc_interrupt(unsigned long arg);
-
-
 /*
  *	Bits in gen_rtc_status.
  */
@@ -99,6 +96,8 @@
 static int stop_rtc_timers;                    /* don't requeue tasks */
 static spinlock_t gen_rtc_lock = SPIN_LOCK_UNLOCKED;
 
+static void gen_rtc_interrupt(unsigned long arg);
+
 /*
  * Routine to poll RTC seconds field for change as often as posible,
  * after first RTC_UIE use timer to reduce polling

WARNING: multiple messages have this Message-ID (diff)
From: Helge Deller <deller@gmx.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	parisc-linux@parisc-linux.org,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Generic RTC driver in 2.4.x
Date: Sun, 12 Jan 2003 13:35:33 +0100	[thread overview]
Message-ID: <200301121333.17077.deller@gmx.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0301121214440.18673-100000@vervain.sonytel.be>

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

On Sunday 12 January 2003 12:33, Geert Uytterhoeven wrote:
> I made some more changes afterwards:
>   - Add forward declaration for gen_rtc_interrupt()

This one should be moved inside the #ifdef CONFIG_GEN_RTC_X section to
avoid "genrtc.c:69: warning: `gen_rtc_interrupt' declared `static' but never defined"
warnings. Please see attached patch.

Or, you could just move the declaration of gen_rtc_interrupt() above the one
from genrtc_troutine(), in which case we wouldn't need the forward declaration at all.

> BTW, perhaps we should move the global RTC_* definitions in <asm/rtc.h> to
> <linux/genrtc.h>, or merge them with the ones in <linux/mc146818rtc.h> and
> move them to <linux/rtc.h>?

IMHO leaving them architecture specific in <asm/rtc.h> seems best to me, and it
leaves the most possibilities to make them later more dependend on the hardware.

Helge


[-- Attachment #2: diff --]
[-- Type: text/plain, Size: 571 bytes --]

--- ./genrtc.c.geert	Sun Jan 12 13:16:40 2003
+++ ./genrtc.c	Sun Jan 12 13:15:18 2003
@@ -66,9 +66,6 @@

 static DECLARE_WAIT_QUEUE_HEAD(gen_rtc_wait);

-static void gen_rtc_interrupt(unsigned long arg);
-
-
 /*
  *	Bits in gen_rtc_status.
  */
@@ -99,6 +96,8 @@
 static int stop_rtc_timers;                    /* don't requeue tasks */
 static spinlock_t gen_rtc_lock = SPIN_LOCK_UNLOCKED;

+static void gen_rtc_interrupt(unsigned long arg);
+
 /*
  * Routine to poll RTC seconds field for change as often as posible,
  * after first RTC_UIE use timer to reduce polling

  parent reply	other threads:[~2003-01-12 12:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-24 13:55 [parisc-linux] Generic RTC driver in 2.4.x? Geert Uytterhoeven
2002-12-24 13:55 ` Geert Uytterhoeven
2002-12-24 23:51 ` [parisc-linux] " Randolph Chung
2002-12-26 17:55   ` Tom Rini
2002-12-28 22:37     ` Geert Uytterhoeven
2003-01-05 14:44       ` Geert Uytterhoeven
2003-01-05 14:44       ` Geert Uytterhoeven
2003-01-10 20:05         ` [parisc-linux] Generic RTC driver in 2.4.x Geert Uytterhoeven
2003-01-10 20:05         ` Geert Uytterhoeven
2003-01-10 20:05           ` Geert Uytterhoeven
2003-01-11 19:50           ` [parisc-linux] " Helge Deller
2003-01-12 11:33             ` Geert Uytterhoeven
2003-01-12 11:33             ` Geert Uytterhoeven
2003-01-12 11:33               ` Geert Uytterhoeven
2003-01-12 12:35               ` [parisc-linux] " Helge Deller
2003-01-12 12:35               ` Helge Deller [this message]
2003-01-12 12:35                 ` Helge Deller
2003-01-12 21:49                 ` [parisc-linux] " Richard Zidlicky
2003-01-12 21:49                   ` Richard Zidlicky
2003-01-12 21:49                 ` [parisc-linux] " Richard Zidlicky
2003-01-30 18:03           ` Tom Rini
2003-01-30 18:03           ` Tom Rini
2003-01-30 18:03             ` Tom Rini
2003-01-31 17:43             ` [parisc-linux] " Geert Uytterhoeven
2003-01-31 17:43               ` Geert Uytterhoeven
2003-01-31 17:43             ` [parisc-linux] " Geert Uytterhoeven
2002-12-28 22:37     ` [parisc-linux] Generic RTC driver in 2.4.x? Geert Uytterhoeven
2002-12-26 17:55   ` Tom Rini
2002-12-24 23:51 ` Randolph Chung

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=200301121333.17077.deller@gmx.de \
    --to=deller@gmx.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=parisc-linux@parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.