LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Christoph Lameter <cl@linux.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Mikael Starvik <starvik@axis.com>,
	Jesper Nilsson <jesper.nilsson@axis.com>,
	linux-cris-kernel@axis.com
Subject: Re: mm/percpu.c: use smarter memory allocation for struct pcpu_alloc_info (crisv32 hang)
Date: Mon, 27 Nov 2017 12:33:35 -0800	[thread overview]
Message-ID: <20171127203335.GQ983427@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1711271515540.5925@knanqh.ubzr>

Hello,

On Mon, Nov 27, 2017 at 03:31:52PM -0500, Nicolas Pitre wrote:
> So IMHO I don't think reverting the commit is the right thing to do. 
> That commit is clearly not at fault here.

It's not about the blame.  We just want to avoid breaking boot in a
way which is difficult to debug.  Once cris is fixed, we can re-apply
the patch.

Thanks.

-- 
tejun

  reply	other threads:[~2017-11-27 20:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 20:57 [PATCH] mm/percpu.c: use smarter memory allocation for struct pcpu_alloc_info Nicolas Pitre
2017-10-03 21:05 ` Tejun Heo
2017-10-03 22:29   ` Nicolas Pitre
2017-10-03 22:36     ` Tejun Heo
2017-10-03 23:48       ` Dennis Zhou
2017-10-04  0:13         ` Nicolas Pitre
2017-10-04 14:15     ` Tejun Heo
2017-11-18 18:25     ` mm/percpu.c: use smarter memory allocation for struct pcpu_alloc_info (crisv32 hang) Guenter Roeck
2017-11-19 20:36       ` Nicolas Pitre
2017-11-20  2:03         ` Guenter Roeck
2017-11-20  4:08           ` Nicolas Pitre
2017-11-20  5:05             ` Guenter Roeck
2017-11-20 18:18               ` Nicolas Pitre
2017-11-20 18:51                 ` Guenter Roeck
2017-11-20 20:21                   ` Nicolas Pitre
2017-11-20 21:11                     ` Guenter Roeck
2017-11-21  0:28                       ` Nicolas Pitre
2017-11-21  1:48                         ` Guenter Roeck
2017-11-21  3:50                           ` Nicolas Pitre
2017-11-22 15:34                             ` Jesper Nilsson
2017-11-22 20:17                               ` Nicolas Pitre
2017-11-23  7:56                                 ` Jesper Nilsson
2017-11-27 19:41       ` Tejun Heo
2017-11-27 20:31         ` Nicolas Pitre
2017-11-27 20:33           ` Tejun Heo [this message]
2017-11-27 20:51             ` Nicolas Pitre
2017-11-27 20:54               ` Tejun Heo
2017-11-27 21:11                 ` Guenter Roeck
2017-11-28  8:19               ` Jesper Nilsson

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=20171127203335.GQ983427@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=cl@linux.com \
    --cc=jesper.nilsson@axis.com \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@roeck-us.net \
    --cc=nicolas.pitre@linaro.org \
    --cc=starvik@axis.com \
    /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;
as well as URLs for NNTP newsgroup(s).