mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: emacs visiting of [patch 2.6.19-rc6] Documentation/rtc.txt updates (for rtc class)
Date: Fri, 17 Nov 2006 12:55:25 +0000 (UTC)	[thread overview]
Message-ID: <slrnelrcnc.7lr.olecom@flower.upol.cz> (raw)
In-Reply-To: <200611162309.31879.david-b@pacbell.net>

On 2006-11-17, David Brownell wrote:
> Index: g26/Documentation/rtc.txt

Just another emacs visiting...
Will try to build and reboot to test stuff tomorrow.

Index: 2.6_current/Documentation/rtc.txt
===================================================================
--- 2.6_current.orig/Documentation/rtc.txt	2006-11-17 13:33:10.979411250 +0100
+++ 2.6_current/Documentation/rtc.txt	2006-11-17 13:33:40.981286250 +0100
@@ -18,7 +18,7 @@
 
     *	/dev/rtc ... is the RTC provided by PC compatible systems,
 	so it's not very portable to non-x86 systems.
-    
+
     *	/dev/rtc0, /dev/rtc1 ... are part of a framework that's
 	supported by a wide variety of RTC chips on all systems.
 
@@ -86,9 +86,9 @@
 interrupt handler is only a few lines of code to minimize any possibility
 of this effect.
 
-Also, if the kernel time is synchronized with an external source, the 
-kernel will write the time back to the CMOS clock every 11 minutes. In 
-the process of doing this, the kernel briefly turns off RTC periodic 
+Also, if the kernel time is synchronized with an external source, the
+kernel will write the time back to the CMOS clock every 11 minutes. In
+the process of doing this, the kernel briefly turns off RTC periodic
 interrupts, so be aware of this if you are doing serious work. If you
 don't synchronize the kernel time with an external source (via ntp or
 whatever) then the kernel will keep its hands off the RTC, allowing you


  parent reply	other threads:[~2006-11-17 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17  7:09 David Brownell
2006-11-17 11:45 ` Oleg Verych
2006-11-17 12:55 ` Oleg Verych [this message]
2006-11-19 23:53 ` 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=slrnelrcnc.7lr.olecom@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®