From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Define _TIF_POLLING_NRFLAG
Date: Fri, 9 May 2014 15:46:20 +0100 [thread overview]
Message-ID: <20140509144619.GH7950@arm.com> (raw)
In-Reply-To: <20140509140316.GU2844@laptop.programming.kicks-ass.net>
On Fri, May 09, 2014 at 03:03:16PM +0100, Peter Zijlstra wrote:
> On Fri, May 09, 2014 at 12:57:45PM +0100, Mark Brown wrote:
> > From: Mark Brown <broonie@linaro.org>
> >
> > arm64 defines TIF_POLLING_NRFLAG but not the corresponding shifted version,
> > breaking the build with next-20140509 due to fd99f91aa007b (sched/idle:
> > Avoid spurious wakeup IPIs) which added a reference to the shifted version
> > which is present on most arches.
>
> Sorry about that,
>
> Acked-by: Peter Zijlstra <peterz@infradead.org>
I replied already in another thread. I don't think we need this bit at
all.
> Should I get it in -tip so borkage and fix come in through the same
> tree, or what's the preferred routing?
Whatever it's easier for you.
--
Catalin
prev parent reply other threads:[~2014-05-09 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 11:57 [PATCH] arm64: Define _TIF_POLLING_NRFLAG Mark Brown
2014-05-09 14:03 ` Peter Zijlstra
2014-05-09 14:46 ` Catalin Marinas [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=20140509144619.GH7950@arm.com \
--to=catalin.marinas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.