From: john stultz <johnstul@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
Wolfram Sang <w.sang@pengutronix.de>
Subject: [GIT pull] rtc fixes for 2.6.39
Date: Thu, 05 May 2011 12:34:19 -0700 [thread overview]
Message-ID: <1304624059.20980.10.camel@work-vm> (raw)
Hey Thomas,
Here are some urgent 2.6.39 boot fixups from Wolfram for RTC devices
that register themselves before they are finished initializing.
They are available in the git repository at:
git://git.linaro.org/people/jstultz/linux.git fortglx/39/tip/timers/rtc
Wolfram Sang (3):
rtc: mxc: fix crash on boot
rtc: davinci: fix crash on boot
rtc: ep93xx: fix crash on boot
drivers/rtc/rtc-davinci.c | 5 +++--
drivers/rtc/rtc-ep93xx.c | 5 ++---
drivers/rtc/rtc-mxc.c | 19 +++++++++++--------
3 files changed, 16 insertions(+), 13 deletions(-)
next reply other threads:[~2011-05-05 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 19:34 john stultz [this message]
2011-05-06 0:23 ` [GIT pull] rtc fixes for 2.6.39 Thomas Gleixner
2011-05-06 2:18 ` john stultz
2011-05-10 0:28 ` john stultz
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=1304624059.20980.10.camel@work-vm \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=w.sang@pengutronix.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