mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Alessandro Zummo <a.zummo@towertech.it>
Cc: John Stultz <john.stultz@linaro.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Stefani Seibold <stefani@seibold.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>,
	"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
	Prarit Bhargava <prarit@redhat.com>
Subject: Re: X86: Impossible select Enhanced Real Time Clock Support (legacy PC RTC driver)
Date: Tue, 6 May 2014 00:34:41 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1405060026210.21408@eddie.linux-mips.org> (raw)
In-Reply-To: <20140428202034.782de089@linux.lan.towertech.it>

On Mon, 28 Apr 2014, Alessandro Zummo wrote:

> > But it sounds like the driver/char/rtc bit is dead code, and needs a
> > cleanup? Or is there some use of that code that you need that the
> > generic RTC layer doesn't have?
> 
>  as far as I know, no recent distribution is using the old code anymore 
>  and the new (well, not so new anymore) framework provides the same 
>  functionality.

 Well, the handling of update-ended interrupts is still missing, as is 
some non-x86 stuff I posted a fix for recently (still pending review, can 
you please look into it sometime?).

  Maciej

  parent reply	other threads:[~2014-05-05 23:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 19:05 Stefani Seibold
2014-04-21 17:58 ` Randy Dunlap
2014-04-28 18:16   ` John Stultz
2014-04-28 18:20     ` Alessandro Zummo
2014-05-02 20:03       ` Stefani Seibold
2014-05-05 23:34       ` Maciej W. Rozycki [this message]
2014-05-06  9:56         ` [rtc-linux] " Alessandro Zummo

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=alpine.LFD.2.11.1405060026210.21408@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=a.zummo@towertech.it \
    --cc=greg@kroah.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=stefani@seibold.net \
    /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

all inboxes | Powered by JetHome®