From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
rusty@rustcorp.com.au
Subject: Re: [PATCH -next] at91rm9200 vs cpumask changes
Date: Fri, 28 Nov 2008 21:59:12 +1100 [thread overview]
Message-ID: <20081128215912.f12c644e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20081128103913.GA8488@x200.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Hi Alexey,
On Fri, 28 Nov 2008 13:39:13 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> --- a/arch/arm/mach-at91/at91rm9200_time.c
> +++ b/arch/arm/mach-at91/at91rm9200_time.c
> @@ -169,7 +169,6 @@ static struct clock_event_device clkevt = {
> .features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT,
> .shift = 32,
> .rating = 150,
> - .cpumask = CPU_MASK_CPU0,
> .set_next_event = clkevt32k_next_event,
> .set_mode = clkevt32k_mode,
> };
> @@ -197,7 +196,7 @@ void __init at91rm9200_timer_init(void)
> clkevt.mult = div_sc(AT91_SLOW_CLOCK, NSEC_PER_SEC, clkevt.shift);
> clkevt.max_delta_ns = clockevent_delta2ns(AT91_ST_ALMV, &clkevt);
> clkevt.min_delta_ns = clockevent_delta2ns(2, &clkevt) + 1;
> - clkevt.cpumask = cpumask_of_cpu(0);
> + clkevt.cpumask = cpumask_of(0);
> clockevents_register_device(&clkevt);
>
> /* register clocksource */
This patch is already in the rr tree today. But thanks for the patch.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-11-28 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 10:39 [PATCH -next] at91rm9200 vs cpumask changes Alexey Dobriyan
2008-11-28 10:59 ` Stephen Rothwell [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=20081128215912.f12c644e.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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