From: Thomas Gleixner <tglx@linutronix.de>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Rabin Vincent" <rabin.vincent@stericsson.com>,
"Yang Honggang (Joseph)" <eagle.rtlinux@gmail.com>
Subject: Re: [GIT PULL] RTC fixes for 3.2
Date: Fri, 2 Dec 2011 11:55:56 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1112021155330.2735@ionos> (raw)
In-Reply-To: <1322784117.21423.155.camel@work-vm>
On Thu, 1 Dec 2011, john stultz wrote:
> Hey Thomas,
> I just wanted to ping you again on the following fixes for 3.2. I've
> added a clocksource fix as well to the queue.
>
> The patches available in the git repository at:
> git://git.linaro.org/people/jstultz/linux.git fortglx/3.2/tip/timers/urgent
Pulled, thanks
tglx
prev parent reply other threads:[~2011-12-02 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 3:32 [GIT PULL] RTC fixes for 3.2 John Stultz
2011-12-02 0:01 ` john stultz
2011-12-02 10:55 ` Thomas Gleixner [this message]
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=alpine.LFD.2.02.1112021155330.2735@ionos \
--to=tglx@linutronix.de \
--cc=arve@android.com \
--cc=eagle.rtlinux@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin.vincent@stericsson.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