From: John Stultz <john.stultz@linaro.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "John Stultz" <john.stultz@linaro.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Meelis Roos" <mroos@ut.ee>,
"Toralf Förster" <toralf.foerster@gmx.de>,
"Peter Zijlstra" <peterz@infradead.org>
Subject: [PATCH 0/2] Alarmtimer fixes for 3.0
Date: Tue, 21 Jun 2011 16:52:51 -0700 [thread overview]
Message-ID: <1308700373-18415-1-git-send-email-john.stultz@linaro.org> (raw)
Hey Thomas,
Here are two alarmtimer fixes that should go in for 3.0.
The first is a fix to check for rtc devices on demand, to better
handle late rtc device driver loading. And the second makes sure
we report an error to apps using alarmtiemrs if there is no backing
RTC device.
Let me know if you have any issues with these.
Both of these patches are available in the git repository at:
git://git.linaro.org/people/jstultz/linux.git fortglx/3.0/tip/timers/alarmtimers
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Meelis Roos <mroos@ut.ee>
CC: Toralf Förster <toralf.foerster@gmx.de>
CC: Richard Weinberger <richard@nod.at
CC: Peter Zijlstra <peterz@infradead.org>
John Stultz (2):
alarmtimers: Handle late rtc module loading
alarmtimers: Return -ENOTSUPP if no RTC device is present
kernel/time/alarmtimer.c | 158 +++++++++++++++++++++++++--------------------
1 files changed, 88 insertions(+), 70 deletions(-)
--
1.7.3.2.146.gca209
next reply other threads:[~2011-06-21 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 23:52 John Stultz [this message]
2011-06-21 23:52 ` [PATCH 1/2] alarmtimers: Handle late rtc module loading John Stultz
2011-06-21 23:52 ` [PATCH 2/2] alarmtimers: Return -ENOTSUPP if no RTC device is present John Stultz
2011-06-22 9:19 ` richard -rw- weinberger
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=1308700373-18415-1-git-send-email-john.stultz@linaro.org \
--to=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@ut.ee \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=toralf.foerster@gmx.de \
/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®