From: john stultz <johnstul@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make clocksource name const
Date: Mon, 04 Apr 2011 11:22:53 -0700 [thread overview]
Message-ID: <1301941373.2319.28.camel@work-vm> (raw)
In-Reply-To: <alpine.LFD.2.00.1104041943580.19945@localhost6.localdomain6>
On Mon, 2011-04-04 at 19:44 +0200, Thomas Gleixner wrote:
> On Mon, 4 Apr 2011, john stultz wrote:
>
> > On Sat, 2011-04-02 at 15:11 +0100, Russell King - ARM Linux wrote:
> > > Has this patch been rejected?
> >
> > No, just my clocksource cleanups tree didn't get pulled for 2.6.39.
>
> Crap.
Sorry, I probably should have nagged you a bit more.
> > Thomas: The commit can be found here:
> > http://git.linaro.org/gitweb?p=people/jstultz/linux.git;a=commit;h=36d8593ec74dc04d3bd7c1c897a7b7cfbd0b0dc6
>
> Is there more stuff pending ?
Just clocksource_register_hz/khz bits, but those aren't critical, and
can be moved in slowly via arch maintainers if you're not comfortable
with them. I also need to refresh some of them, as there were some
collisions in the merge window.
thanks
-john
next prev parent reply other threads:[~2011-04-04 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 15:34 [PATCH] Make clocksource name const Russell King - ARM Linux
2011-02-21 18:51 ` john stultz
2011-04-02 14:11 ` Russell King - ARM Linux
2011-04-02 19:08 ` Thomas Gleixner
2011-04-02 19:31 ` Thomas Gleixner
2011-04-04 17:42 ` john stultz
2011-04-04 17:44 ` Thomas Gleixner
2011-04-04 18:22 ` john stultz [this message]
2011-04-04 19:07 ` Thomas Gleixner
2011-04-04 20:25 ` [PATCH] Make clocksource name const... RTC: Fix early irqs caused by calling rtc_set_alarm too early Konrad Rzeszutek Wilk
2011-04-04 21:07 ` 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=1301941373.2319.28.camel@work-vm \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.