mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Mel Gorman <mgorman@suse.de>
Cc: Christoph Lameter <cl@linux.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] percpu: Resolve ambiguities in __get_cpu_var/cpumask_var_t -fix
Date: Tue, 9 Sep 2014 07:14:27 +0900	[thread overview]
Message-ID: <20140908221427.GA3806@mtj.dyndns.org> (raw)
In-Reply-To: <20140908220654.GO17501@suse.de>

On Mon, Sep 08, 2014 at 11:06:54PM +0100, Mel Gorman wrote:
> A commit in linux-next was causing boot to fail and bisection identified
> the patch "percpu: Resolve ambiguities in __get_cpu_var/cpumask_var_".
> The commit ID is worthless as it's a linux-next commit. One of the changes

It is actually a stable commit ID.  I'll add the commit ID in the
change log.

> in that patch looks very suspicious. Reverting the full patch fixes boot
> as does this fixlet.

Applying to percpu/for-3.18-consistent-ops.

Thanks.

-- 
tejun

  reply	other threads:[~2014-09-08 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 22:06 Mel Gorman
2014-09-08 22:14 ` Tejun Heo [this message]
2014-09-08 23:46 ` Christoph Lameter
2014-09-09  0:35   ` Tejun Heo
2014-09-09  5:55     ` Ted Percival
2014-09-09  0:21 ` David Rientjes

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=20140908221427.GA3806@mtj.dyndns.org \
    --to=tj@kernel.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    /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

Powered by JetHome