From: Andrew Morton <akpm@linux-foundation.org>
To: Ed Swierk <eswierk@aristanetworks.com>
Cc: a.zummo@towertech.it, rtc-linux@googlegroups.com,
tglx@linutronix.de, mingo@redhat.com,
linux-kernel@vger.kernel.org,
Roman Zippel <zippel@linux-m68k.org>
Subject: Re: [PATCH] rtc: add rtc_systohc for ntp use
Date: Mon, 2 Feb 2009 14:26:13 -0800 [thread overview]
Message-ID: <20090202142613.2ca84f52.akpm@linux-foundation.org> (raw)
In-Reply-To: <1233018262.14510.111.camel@localhost.localdomain>
On Mon, 26 Jan 2009 17:04:22 -0800
Ed Swierk <eswierk@aristanetworks.com> wrote:
> Following up to Alessandro's RFC of 10 Nov 2008, this patch implements
> rtc_systohc() to update the configured rtc device (cmos, i2c, etc.) from
> the ntp-synchronized system clock. It changes the ntp update code to
> call rtc_systohc() rather than update_persistent_clock() which (at least
> on x86) always updates the cmos rtc.
>
> No attempt is made to compensate for the 500-ms delay imposed when
> setting a cmos rtc chip. If you actually have a cmos rtc you can stick
> with the existing code, but at some point it would be nice to unify
> these.
I don't get this. Do we not currently update the cmos clock in
response to NTP controls? Does the patch now alter this policy, by now
updating the RTC?
IOW: what effect does this patch actually have upon the kernel?
Please cc Roman on NTP changes. Roman, please consider sending in a
MAINTAINERS patch for this.
Please use scripts/checkpatch.pl.
Please fix the checkpatch warnings which this patch emits.
When fixing the extern-declaration-in-C warning, please consider
dropping the ifdefs around the rtc_systohc() declaration in the header
file. They're not really needed.
next prev parent reply other threads:[~2009-02-02 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 1:04 [PATCH] rtc: add rtc_systohc for ntp use Ed Swierk
2009-02-02 22:26 ` Andrew Morton [this message]
2009-02-03 6:09 ` 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=20090202142613.2ca84f52.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=eswierk@aristanetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rtc-linux@googlegroups.com \
--cc=tglx@linutronix.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 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.