From: john stultz <johnstul@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] RTC changes for 3.4
Date: Wed, 01 Feb 2012 18:56:45 -0800 [thread overview]
Message-ID: <1328151405.2342.113.camel@work-vm> (raw)
Hey Thomas,
Just wanted to send you my current 3.4 queue for RTC changes.
These address the issues that we had to revert similar patches for late
in the 3.2-rc period. I'm sending them now so there is enough time to
make sure any other issues that might crop up can be handled.
Again, since tip/timers/core hasn't been updated since 3.3 was out,
these are against Linus' head (actually, from a week or so ago). Let me
know if you'd like me to base them off of something else.
thanks
-john
The patches are available in the git repository at:
git://git.linaro.org/people/jstultz/linux.git fortglx/3.4/rtc
John Stultz (1):
rtc: Avoid setting alarm to a time in the past
NeilBrown (1):
rtc: Expire alarms after the time is set. (v2)
Rabin Vincent (1):
rtc: Disable the alarm in the hardware (v2)
drivers/rtc/interface.c | 30 +++++++++++++++++++++++++++---
1 files changed, 27 insertions(+), 3 deletions(-)
reply other threads:[~2012-02-02 2:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1328151405.2342.113.camel@work-vm \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).