From: Prarit Bhargava <prarit@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: corbet@lwn.net, rtc-linux@googlegroups.com,
linux-doc@vger.kernel.org, a.zummo@towertech.it,
Prarit Bhargava <prarit@redhat.com>
Subject: [PATCH 0/2] Documentation, update RTC documentation
Date: Mon, 16 Mar 2015 11:58:53 -0400 [thread overview]
Message-ID: <1426521535-12501-1-git-send-email-prarit@redhat.com> (raw)
Documentation/rtc.txt is a combination of two files, a real documentation
file and a test program. Splitting these up into two files is a good idea
for automated testing. While testing on an AMD based system it was noticed
that the RTC was not behaving properly which lead to a possible bug in the
BIOS (the analysis of which is still ongoing). rtctest.c returned a false
positive because it does not check the time between interrupts is what was
expected. This patchset adds Documentation/rtc, splits the rtc.txt into two
files and updates the test to verify the passage of time.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Prarit Bhargava (2):
Documentation, add rtc directory and split up rtc.txt
Documentation, update rtctest.c to verify passage of time
Documentation/rtc.txt | 469 -------------------------------------------
Documentation/rtc/rtc.txt | 207 +++++++++++++++++++
Documentation/rtc/rtctest.c | 271 +++++++++++++++++++++++++
3 files changed, 478 insertions(+), 469 deletions(-)
delete mode 100644 Documentation/rtc.txt
create mode 100644 Documentation/rtc/rtc.txt
create mode 100644 Documentation/rtc/rtctest.c
--
1.7.9.3
next reply other threads:[~2015-03-16 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 15:58 Prarit Bhargava [this message]
2015-03-16 15:58 ` [PATCH 1/2] Documentation, add rtc directory and split up rtc.txt Prarit Bhargava
2015-03-16 15:58 ` [PATCH 2/2] Documentation, update rtctest.c to verify passage of time Prarit Bhargava
2015-03-16 17:10 ` [PATCH 0/2] Documentation, update RTC documentation Jonathan Corbet
2015-03-18 19:12 ` Prarit Bhargava
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=1426521535-12501-1-git-send-email-prarit@redhat.com \
--to=prarit@redhat.com \
--cc=a.zummo@towertech.it \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome