All of lore.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: takata@linux-m32r.org,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	davem@davemloft.net, wli@holomorphy.com,
	Joel Becker <Joel.Becker@oracle.com>
Subject: Re: [RFC][PATCH] Unify interface to persistent CMOS/RTC/whatever clock
Date: Wed, 16 Aug 2006 18:49:50 -0700	[thread overview]
Message-ID: <1155779390.22876.0.camel@localhost.localdomain> (raw)
In-Reply-To: <1155768332.6785.58.camel@localhost.localdomain>

On Wed, 2006-08-16 at 15:45 -0700, john stultz wrote:
> My first pass at this can be found below. There are a few arches
> (specifically: m32r, s390, sparc, sparc64) where I just didn't know what
> to do, or where I suspect I didn't get it right, so I've CC'ed those
> maintainers for suggestions.

Just realized I skipped the ARM arches. I'll get that fixed (or atleast
make an attempt at it) before the next release.

thanks
-john


  reply	other threads:[~2006-08-17  1:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 22:45 [RFC][PATCH] Unify interface to persistent CMOS/RTC/whatever clock john stultz
2006-08-17  1:49 ` john stultz [this message]
2006-08-17  9:20 ` Martin Schwidefsky
  -- strict thread matches above, loose matches on Subject: below --
2006-08-17  5:47 David Brownell
2006-08-17 19:08 ` john stultz
2006-08-17 20:28   ` David Brownell
2006-08-17 21:42     ` john stultz
2006-08-17 23:41       ` David Brownell
2006-08-18  0:07         ` john stultz
2006-08-18  1:38           ` David Brownell
2006-08-18 23:36             ` john stultz
2006-08-19 16:39               ` David Brownell
2006-08-19 16:44                 ` David Brownell
2006-08-18  5:50           ` David Brownell

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=1155779390.22876.0.camel@localhost.localdomain \
    --to=johnstul@us.ibm.com \
    --cc=Joel.Becker@oracle.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=takata@linux-m32r.org \
    --cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.