From: john stultz <johnstul@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
Bryan Henderson <bryanh@giraffe-data.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: [GIT pull] RTC fixes for 3.0
Date: Fri, 03 Jun 2011 18:07:00 -0700 [thread overview]
Message-ID: <1307149620.11492.64.camel@work-vm> (raw)
Hey Thomas,
Here are some RTC fixes needed for 3.0. Please take a look at them and
queue them for Linus.
git://git.linaro.org/people/jstultz/linux.git fortglx/3.0/tip/timers/rtc
John Stultz (1):
rtc: Fix ioctl error path return
Mark Brown (1):
rtc: Staticize non-exported __rtc_set_alarm()
drivers/rtc/interface.c | 2 +-
drivers/rtc/rtc-dev.c | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
reply other threads:[~2011-06-04 1:07 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=1307149620.11492.64.camel@work-vm \
--to=johnstul@us.ibm.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=bryanh@giraffe-data.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