From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] ARM: smp_twd: create a percpu reference to the clockevent
Date: Tue, 13 Dec 2011 12:31:03 +0100 [thread overview]
Message-ID: <CACRpkdYEitq9a7ZPMP-pHP7NtRPZTbmzJmayFDBA210rkwZaKQ@mail.gmail.com> (raw)
In-Reply-To: <20111212134904.GV14542@n2100.arm.linux.org.uk>
On Mon, Dec 12, 2011 at 2:49 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Mon, Dec 12, 2011 at 10:57:10AM +0100, Linus Walleij wrote:
>> ?static unsigned long twd_timer_rate;
>> +static DEFINE_PER_CPU(struct clock_event_device *, twd_ce);
>>
>> ?static struct clock_event_device __percpu **twd_evt;
>
> So, one pointer to the clock_event_device is not enough? ?Could we have
> one or the other?
Bah, just me being lame and not seeing that Marc already made
these events per-cpu.
I'll update the CPUfreq patch and drop this crap.
Thanks,
Linus Walleij
prev parent reply other threads:[~2011-12-13 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 9:57 [PATCH 2/4] ARM: smp_twd: create a percpu reference to the clockevent Linus Walleij
2011-12-12 13:49 ` Russell King - ARM Linux
2011-12-13 11:31 ` Linus Walleij [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=CACRpkdYEitq9a7ZPMP-pHP7NtRPZTbmzJmayFDBA210rkwZaKQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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).