public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>,
	Roman Zippel <zippel@linux-m68k.org>,
	George Anzinger <george@mvista.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCHSET] Time: Generic Timeofday Subsystem (v B17)
Date: Mon, 23 Jan 2006 01:39:38 +0200	[thread overview]
Message-ID: <20060122233938.GA31392@linux-sh.org> (raw)
In-Reply-To: <1137801626.27699.279.camel@cog.beaverton.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

On Fri, Jan 20, 2006 at 04:00:26PM -0800, john stultz wrote:
> The patchset applies against the current 2.6.16-rc1-git.
> 
> The complete patchset can be found here:
> 	http://sr71.net/~jstultz/tod/
> 
> As always, feedback, suggestions and bug-reports are always appreciated.
> 
Patches weren't explicitly mentioned, but I'm assuming they're also
welcome ;-)

At first glance the register/unregister interface is a bit
unconventional, but I have a few trivial patches to get those fixed up,
which I'll send to you separately.

It looks like struct clocksource will also need suspend/resume ops,
since it's defining its own sysclass (so there's no overlap with the
timer sysclass that several other architectures setup to deal with this).
I haven't done that yet, but if there's interest, I'll hack something up.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-01-22 23:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21  0:00 [PATCHSET] Time: Generic Timeofday Subsystem (v B17) john stultz
2006-01-22 23:39 ` Paul Mundt [this message]
2006-01-23 20:10   ` john stultz
2006-01-24  0:18     ` Paul Mundt

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=20060122233938.GA31392@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=george@mvista.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=ulrich.windl@rz.uni-regensburg.de \
    --cc=zippel@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