From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christoph Lameter <cl@linux.com>
Cc: Tejun Heo <tj@kernel.org>, Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@elte.hu>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH percpu/for-3.18-consistent-ops] Revert "powerpc: Replace __get_cpu_var uses"
Date: Thu, 28 Aug 2014 07:49:37 +1000 [thread overview]
Message-ID: <20140828074937.47020590@canb.auug.org.au> (raw)
In-Reply-To: <alpine.DEB.2.11.1408271055030.17080@gentwo.org>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
Hi Christoph,
On Wed, 27 Aug 2014 10:56:27 -0500 (CDT) Christoph Lameter <cl@linux.com> wrote:
>
> On Wed, 27 Aug 2014, Tejun Heo wrote:
>
> > Chrisoph, let's route the updated patch through powerpc tree.
>
> Ok. Once I figure out what went wrong. This went through Feng's build
> system and I though he did a powerpc build. So it must be a difference
> configuration on powerpc.
Were the patches tested on top of v3.17-rc1? My build was a powerpc
ppc64_defconfig. It is possible that some other change interacted with
this, but there are not many other arch/powerpc changes after v3.17-rc1
and none seem obvious.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-27 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 4:22 linux-next: build failure after merge of the percpu tree Stephen Rothwell
2014-08-27 15:26 ` [PATCH percpu/for-3.18-consistent-ops] Revert "powerpc: Replace __get_cpu_var uses" Tejun Heo
2014-08-27 15:56 ` Christoph Lameter
2014-08-27 21:49 ` Stephen Rothwell [this message]
2014-08-27 23:23 ` Christoph Lameter
2014-08-27 21:43 ` Stephen Rothwell
2014-08-27 21:49 ` Tejun Heo
2014-08-27 21:54 ` Christoph Lameter
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=20140828074937.47020590@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=benh@kernel.crashing.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rusty@rustcorp.com.au \
--cc=tj@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