From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: move read_{boot, persistent}_clock to the architecture level
Date: Sat, 05 May 2012 19:16:50 +0200 [thread overview]
Message-ID: <f91fc31ded5595a14101dffb4cab937f@localhost> (raw)
In-Reply-To: <20120505164753.GP897@n2100.arm.linux.org.uk>
On Sat, 5 May 2012 17:47:53 +0100, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Sat, Apr 28, 2012 at 01:45:45PM +0100, Marc Zyngier wrote:
>> At the moment, read_persistent_clock is implemented at the
>> platform level, which makes it impossible to compile these
>> platforms in a single kernel.
>>
>> Implement these two functions at the architecture level, and
>> provide a thin registration interface for both read_boot_clock
>> and read_persistent_clock. The two affected platforms (OMAP and
>> Tegra) are converted at the same time.
>>
>> Compile tested only.
>
> As this now has tested-bys for OMAP and Tegra, I guess it's ready.
Who's
> planning to take this?
If you're happy to take it, and unless someone objects to it, I'll put it
in the patch system.
Thanks Stephen and Tony for testing it.
M.
--
Fast, cheap, reliable. Pick two.
next prev parent reply other threads:[~2012-05-05 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 12:45 [PATCH] ARM: move read_{boot, persistent}_clock to the architecture level Marc Zyngier
2012-05-01 18:11 ` Stephen Warren
2012-05-05 0:13 ` [PATCH] ARM: move read_{boot,persistent}_clock " Tony Lindgren
2012-05-05 16:47 ` [PATCH] ARM: move read_{boot, persistent}_clock " Russell King - ARM Linux
2012-05-05 17:16 ` Marc Zyngier [this message]
2012-05-05 17:20 ` Russell King - ARM Linux
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=f91fc31ded5595a14101dffb4cab937f@localhost \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).