From: Peter Zijlstra <peterz@infradead.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] timers: Allocate per-cpu tvec_base's statically
Date: Mon, 30 Mar 2015 12:27:26 +0200 [thread overview]
Message-ID: <20150330102726.GS23123@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKohponL7cUFUR4eM5QyO8dxrbZGahGU9i-C8qwA-Yx_K1MseQ@mail.gmail.com>
On Mon, Mar 30, 2015 at 03:25:36PM +0530, Viresh Kumar wrote:
> On 30 March 2015 at 13:48, Peter Zijlstra <peterz@infradead.org> wrote:
> > I did the below on top; I'll sit on these patches for a wee while in the
> > hope of the blackfin maintainer explaining his reasons for wrecking
> > ____cacheline_aligned.
>
> Two things I wanted to mention:
>
> 1.) We may need to drop the patch 2/3 as that breaks build for xtensa and tile.
>
> kernel/time/timer.c: In function 'init_timers_cpu':
> kernel/time/timer.c:1539:1: error: section attribute cannot be
> specified for local variables
> Can these be fixed somehow ?
Hmm, is your xtensa/tile compiler different from your others? But no,
I think we need to move it back to global scope. Lemme go do that.
next prev parent reply other threads:[~2015-03-30 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 5:17 [PATCH 0/3] timers: Allocate per-cpu tvec_base's statically Viresh Kumar
2015-03-30 5:17 ` [PATCH 1/3] timer: " Viresh Kumar
2015-03-31 7:45 ` Ingo Molnar
2015-03-31 11:32 ` Viresh Kumar
2015-03-30 5:17 ` [PATCH 2/3] timer: Limit the scope of __tvec_bases to init_timers_cpu() Viresh Kumar
2015-03-30 5:17 ` [PATCH 3/3] timer: Don't initialize tvec_base on hotplug Viresh Kumar
2015-03-30 8:18 ` [PATCH 0/3] timers: Allocate per-cpu tvec_base's statically Peter Zijlstra
2015-03-30 9:55 ` Viresh Kumar
2015-03-30 10:27 ` Peter Zijlstra [this message]
2015-03-30 10:33 ` Viresh Kumar
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=20150330102726.GS23123@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.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