From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Richard Zidlicky <rz@linux-m68k.org>,
rtc-linux@googlegroups.com, linux-parisc@vger.kernel.org,
Development <linux-kernel@vger.kernel.org>,
David, Kyle McMartin <kyle@mcmartin.ca>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
Linux, David@ozlabs.org, Woodhouse <dwmw2@infradead.org>
Subject: Re: [rtc-linux] Re: [PATCH/RFC 0/5] Generic RTC class driver
Date: Mon, 2 Mar 2009 11:03:10 +0100 [thread overview]
Message-ID: <20090302110310.35af50ea@i1501.lan.towertech.it> (raw)
In-Reply-To: <alpine.LRH.2.00.0903021051040.25117@vixen.sonytel.be>
On Mon, 2 Mar 2009 10:54:14 +0100 (CET)
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> wrote:
> Indeed. You can have a working RTC class driver for lots of hardware by just
> writing ca. 100 lines of code on top of the generic framework.
That's true, but we would then have two generic frameworks. And one
of them will have its code scattered all around the kernel.
So you either use the old rtc framework, which is perfectly functional,
or you move to the new rtc lass and write the drivers.
Layering a generic framework over another generic framework
is quite a nonsense .
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2009-03-02 10:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 15:46 [PATCH/RFC 0/5] Generic RTC class driver Geert Uytterhoeven
2009-02-20 15:46 ` [PATCH/RFC 1/5] rtc-parisc: Add missing module alias Geert Uytterhoeven
2009-02-20 15:46 ` [PATCH/RFC 2/5] pa-risc: Rename rtc-parisc to rtc-generic Geert Uytterhoeven
2009-02-20 15:46 ` [PATCH/RFC 3/5] m68k: Enable rtc-generic Geert Uytterhoeven
2009-02-20 15:46 ` [PATCH/RFC 4/5] powerpc: Enable rtc-generic, and kill rtc-ppc Geert Uytterhoeven
2009-02-20 15:46 ` [PATCH/RFC 5/5] rtc: Kill genrtc, as all its users have been converted to rtc-generic Geert Uytterhoeven
2009-02-20 16:04 ` [rtc-linux] [PATCH/RFC 0/5] Generic RTC class driver Alessandro Zummo
2009-02-23 12:34 ` Geert Uytterhoeven
2009-02-23 15:05 ` [rtc-linux] " Alessandro Zummo
2009-02-24 17:56 ` Geert Uytterhoeven
2009-02-24 18:37 ` Alessandro Zummo
2009-02-25 1:14 ` Brad Boyer
2009-02-25 9:58 ` Geert Uytterhoeven
2009-02-24 21:35 ` [rtc-linux] " David Woodhouse
2009-02-24 22:11 ` Alessandro Zummo
2009-02-24 22:32 ` David Woodhouse
2009-02-25 10:00 ` Geert Uytterhoeven
2009-02-25 10:18 ` [rtc-linux] " Alessandro Zummo
2009-02-27 17:17 ` Maciej W. Rozycki
2009-02-27 17:19 ` Alessandro Zummo
2009-02-27 18:55 ` Richard Zidlicky
2009-03-02 9:54 ` Geert Uytterhoeven
2009-03-02 10:03 ` Alessandro Zummo [this message]
2009-03-02 10:28 ` Geert Uytterhoeven
2009-03-02 11:09 ` Alessandro Zummo
2009-03-03 10:41 ` Geert Uytterhoeven
2009-03-03 13:53 ` Alessandro Zummo
2009-03-03 19:06 ` Paul Mundt
2009-03-04 8:26 ` Geert Uytterhoeven
2009-03-04 12:47 ` Alessandro Zummo
2009-03-04 12:51 ` Geert Uytterhoeven
2009-02-25 9:54 ` [rtc-linux] " Geert Uytterhoeven
2009-02-24 18:46 ` Helge Deller
2009-02-25 9:54 ` Geert Uytterhoeven
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=20090302110310.35af50ea@i1501.lan.towertech.it \
--to=alessandro.zummo@towertech.it \
--cc=David@ozlabs.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=dwmw2@infradead.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rtc-linux@googlegroups.com \
--cc=rz@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).