From: Shane McDonald <mcdonald.shane@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make MIPS dynamic clocksource/clockevent clock code generic
Date: Sun, 18 Oct 2009 23:22:43 -0600 [thread overview]
Message-ID: <b2b2f2320910182222y2e3eb5f3qa5010ee60a413141@mail.gmail.com> (raw)
In-Reply-To: <b2b2f2320910182217m31ce0a96g4912eeb9bea5f817@mail.gmail.com>
Hello:
On Sat, Oct 17, 2009 at 4:48 PM, Linus Walleij
<linus.walleij@stericsson.com> wrote:
>
> This moves the clocksource_set_clock() and clockevent_set_clock()
> from the MIPS timer code into clockchips and clocksource where
> it belongs. The patch was triggered by code posted by Mikael
> Pettersson duplicating this code for the IOP ARM system. The
> function signatures where altered slightly to fit into their
> destination header files, unsigned int changed to u32 and inlined.
>
> Signed-off-by: Linus Walleij <linus.walleij@stericsson.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Mikael Pettersson <mikpe@it.uu.se>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> ---
> Ralf has stated in earlier conversation that this should be moved,
> now we risk duplicating code so let's move it.
>
> I don't have access to a MIPS cross-compiler so please can the
> MIPS people test this?
I have tested this patch on an RM7000-based MIPS system. The patch
compiles fine, and the kernel successfully runs. You can add my:
Tested-by: Shane McDonald <mcdonald.shane@gmail.com>
Shane
next prev parent reply other threads:[~2009-10-19 5:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 22:48 Linus Walleij
2009-10-18 22:10 ` Mikael Pettersson
[not found] ` <b2b2f2320910182217m31ce0a96g4912eeb9bea5f817@mail.gmail.com>
2009-10-19 5:22 ` Shane McDonald [this message]
2009-10-20 2:25 ` Ralf Baechle
2009-10-20 3:50 ` Thomas Gleixner
2009-10-20 8:19 ` Mikael Pettersson
2009-10-20 21:27 ` Linus Walleij
2009-10-20 21:56 ` David Daney
2009-10-20 22:16 ` Linus Walleij
2009-10-20 22:44 ` David Daney
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=b2b2f2320910182222y2e3eb5f3qa5010ee60a413141@mail.gmail.com \
--to=mcdonald.shane@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome