public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Alessandro Zummo <a.zummo@towertech.it>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH 4/6] [RFC] RTC: Rework RTC code to use timerlist for events
Date: Mon, 18 Oct 2010 18:34:15 -0700	[thread overview]
Message-ID: <1287452055.2758.62.camel@localhost.localdomain> (raw)
In-Reply-To: <20101018141056.0b916878@linux.lan.towertech.it>

On Mon, 2010-10-18 at 14:10 +0200, Alessandro Zummo wrote:
> On Fri, 15 Oct 2010 17:38:53 -0700
> John Stultz <john.stultz@linaro.org> wrote:
> 
> > This patch reworks a large portion of the generic RTC code
> > to in-effect virtualize the rtc interrupt code.
> > 
> > The current RTC interface is very much a raw hardware interface.
> > Via the proc, /dev/, or sysfs interfaces, applications can set
> > the hardware to trigger interrupts in one of three modes:
> 
>  [...]
> 
> 
>  If everything still works after all those changes,
>  it seems a good thing to me ;)

Heh, well, that's a good bit less resistance then I thought I'd get :)

Not that I'm complaining, but Is there anyone else in the RTC community
that you'd recommend getting feedback from on a change this large? I
just want to try to get any back-to-the-blackboard level feedback early
on if possible.

Also, are there any other RTC test cases (other then whats in
Documentation/rtc.txt) that you might recommend to help insure things
are bug-free before submission?

thanks
-john



  reply	other threads:[~2010-10-19  1:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-16  0:38 [PATCH 0/6] [RFC] A posix clock/timer interface to the RTC John Stultz
2010-10-16  0:38 ` [PATCH 1/6] [RFC] posix clocks: dynamic clock ids John Stultz
2010-10-16  0:38   ` [PATCH 2/6] [RFC] Introduce timerlist infrastructure John Stultz
2010-10-16  0:38     ` [PATCH 3/6] [RFC] hrtimers: Convert hrtimers to use " John Stultz
2010-10-16  0:38       ` [PATCH 4/6] [RFC] RTC: Rework RTC code to use timerlist for events John Stultz
2010-10-16  0:38         ` [PATCH 5/6] [RFC] RTC: Remove UIE emulation John Stultz
2010-10-16  0:38           ` [PATCH 6/6] [RFC] RTC: Add posix clock/timer interface John Stultz
2010-10-18 12:10         ` [PATCH 4/6] [RFC] RTC: Rework RTC code to use timerlist for events Alessandro Zummo
2010-10-19  1:34           ` john stultz [this message]
2010-10-18 14:27   ` [PATCH 1/6] [RFC] posix clocks: dynamic clock ids Richard Cochran
2010-10-18 18:01     ` john stultz
2010-10-18 20:44     ` Thomas Gleixner

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=1287452055.2758.62.camel@localhost.localdomain \
    --to=johnstul@us.ibm.com \
    --cc=a.zummo@towertech.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=tglx@linutronix.de \
    /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