From: John Stultz <john.stultz@linaro.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 0/4] Consolidate i8253 clocksource
Date: Mon, 09 May 2011 16:29:22 -0700 [thread overview]
Message-ID: <1304983762.2939.39.camel@work-vm> (raw)
In-Reply-To: <20110509132738.GB16919@n2100.arm.linux.org.uk>
On Mon, 2011-05-09 at 14:27 +0100, Russell King - ARM Linux wrote:
> Three architectures have an i8253 PIT clocksource, and each duplicates
> the code for this. The initial patch extracts a common implementation
> to drivers/clocksource, and subsequent patches convert each architecture
> to use this copy.
Very cool! The series looks good to me.
Although maybe should we get rid of the inb_p redefinitions in a later
cleanup?
Acked-by: John Stultz <john.stultz@linaro.org>
thanks
-john
prev parent reply other threads:[~2011-05-09 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 13:27 [PATCH 0/4] Consolidate i8253 clocksource Russell King - ARM Linux
2011-05-09 23:29 ` John Stultz [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=1304983762.2939.39.camel@work-vm \
--to=john.stultz@linaro.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.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