From: Tom Rini <trini@kernel.crashing.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Andrew Morton <akpm@osdl.org>,
p_gortmaker@yahoo.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH] don't offer GEN_RTC on ia64
Date: Tue, 06 Apr 2004 22:44:50 +0000 [thread overview]
Message-ID: <20040406224450.GJ31152@smtp.west.cox.net> (raw)
In-Reply-To: <200404061637.48475.bjorn.helgaas@hp.com>
On Tue, Apr 06, 2004 at 04:37:48PM -0600, Bjorn Helgaas wrote:
> On Tuesday 06 April 2004 4:34 pm, Tom Rini wrote:
> > On Tue, Apr 06, 2004 at 04:22:49PM -0600, Bjorn Helgaas wrote:
> >
> > > gen_rtc.c doesn't work on ia64 (we don't have asm/rtc.h, for starters),
> > > so don't offer it there.
> >
> > Why not provide asm/rtc.h and kill off drivers/char/efirtc.c instead? :)
>
> Yeah, I was afraid someone would suggest that :-)
>
> I'd actually like to do that, but that's a longer-term project. And I
> don't know the history behind efi_rtc, so maybe there's a good reason
> for it being separate.
>
> (Actually, it looks to me like gen_rtc.c ought to be killed off as well,
> with both being folded into rtc.c.)
efi_rtc.c just predates genrtc getting into kernel.org, but as it does
come from the m68k folks, it came first :) WRT gen_rtc.c being killed
off, yes, that sounds vaugly like the MIPS varriant of a generic RTC
driver, which is being killed off (which reminds me of some cleanups
suggested by Jun Sun, *sigh*, so much to do, so little time).
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-04-06 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 22:22 [PATCH] don't offer GEN_RTC on ia64 Bjorn Helgaas
2004-04-06 22:34 ` Tom Rini
2004-04-06 22:37 ` Bjorn Helgaas
2004-04-06 22:44 ` Tom Rini [this message]
2004-04-06 23:15 ` David Mosberger
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=20040406224450.GJ31152@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.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