From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux.com>,
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:43:49 +1000 [thread overview]
Message-ID: <20140828074349.10e86372@canb.auug.org.au> (raw)
In-Reply-To: <20140827152609.GA379@htj.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
Hi Tejun,
On Wed, 27 Aug 2014 11:26:09 -0400 Tejun Heo <tj@kernel.org> wrote:
>
> From 23f66e2d661b4d3226d16e25910a9e9472ce2410 Mon Sep 17 00:00:00 2001
> From: Tejun Heo <tj@kernel.org>
> Date: Wed, 27 Aug 2014 11:18:29 -0400
>
> This reverts commit 5828f666c069af74e00db21559f1535103c9f79a due to
> build failure after merging with pending powerpc changes.
I can't see any pending powerpc changes that would obviously affect
this ...
--
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:44 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
2014-08-27 23:23 ` Christoph Lameter
2014-08-27 21:43 ` Stephen Rothwell [this message]
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=20140828074349.10e86372@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=benh@kernel.crashing.org \
--cc=cl@linux-foundation.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