diff for duplicates of <20030112224908.A618@linux-m68k.org> diff --git a/a/1.txt b/N1/1.txt index 7d01cf4..6de91a1 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,18 +1,22 @@ + On Sun, Jan 12, 2003 at 01:35:33PM +0100, Helge Deller wrote: > > 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 +> +> 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. in genrtc the RTC_* defs should be used only for interface definition, unlike rtc.c where they are 1:1 with some obscure bits in the rtc chip and also happen to be the interface.. -It would make sense to merge them into <linux/rtc.h>, whether it is +It would make sense to merge them into <linux/rtc.h>, whether it is a good idea to do it in 2.4 is another question. Stuff that is really hw dependent should use different naming (and stay -in asm/rtc.h of course). +in asm/rtc.h of course). Richard + + +** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ diff --git a/a/content_digest b/N1/content_digest index 359c36c..0f0e954 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,7 +1,7 @@ "ref\0Pine.GSO.4.21.0301121214440.18673-100000@vervain.sonytel.be\0" "ref\0200301121333.17077.deller@gmx.de\0" "From\0Richard Zidlicky <rz@linux-m68k.org>\0" - "Subject\0[parisc-linux] Re: Generic RTC driver in 2.4.x\0" + "Subject\0Re: Generic RTC driver in 2.4.x\0" "Date\0Sun, 12 Jan 2003 22:49:08 +0100\0" "To\0Helge Deller <deller@gmx.de>\0" "Cc\0Geert Uytterhoeven <geert@linux-m68k.org>" @@ -11,23 +11,27 @@ " Linux/m68k <linux-m68k@lists.linux-m68k.org>\0" "\00:1\0" "b\0" + "\n" "On Sun, Jan 12, 2003 at 01:35:33PM +0100, Helge Deller wrote:\n" "\n" "> > BTW, perhaps we should move the global RTC_* definitions in <asm/rtc.h> to\n" "> > <linux/genrtc.h>, or merge them with the ones in <linux/mc146818rtc.h> and\n" "> > move them to <linux/rtc.h>?\n" - "> \n" - "> IMHO leaving them architecture specific in <asm/rtc.h> seems best to me, and it \n" + ">\n" + "> IMHO leaving them architecture specific in <asm/rtc.h> seems best to me, and it\n" "> leaves the most possibilities to make them later more dependend on the hardware.\n" "\n" "in genrtc the RTC_* defs should be used only for interface definition,\n" "unlike rtc.c where they are 1:1 with some obscure bits in the rtc chip\n" "and also happen to be the interface..\n" - "It would make sense to merge them into <linux/rtc.h>, whether it is \n" + "It would make sense to merge them into <linux/rtc.h>, whether it is\n" "a good idea to do it in 2.4 is another question.\n" "Stuff that is really hw dependent should use different naming (and stay\n" - "in asm/rtc.h of course). \n" + "in asm/rtc.h of course).\n" + "\n" + "Richard\n" + "\n" "\n" - Richard + ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ -96c8561c8a45d5ba12b630e72b1e91496d0a33ab6d991dac6f27407b84cb0d43 +bfa8d3e0ae3ea2d49bbb1b5df9809fe5e6e61d25e99327bff32f55026bc196d3
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.