All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qian Cai <cai@lca.pw>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, sergey.senozhatsky.work@gmail.com,
	pmladek@suse.com, rostedt@goodmis.org, peterz@infradead.org,
	david@redhat.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next v4] mm/hotplug: silence a lockdep splat with printk()
Date: Fri, 17 Jan 2020 10:05:12 -0500	[thread overview]
Message-ID: <3B7490FB-E915-4DC7-8739-01EDC023E22E@lca.pw> (raw)
In-Reply-To: <20200117143905.GZ19428@dhcp22.suse.cz>



> On Jan 17, 2020, at 9:39 AM, Michal Hocko <mhocko@kernel.org> wrote:
> 
> Thanks a lot. Having it in a separate patch would be great.

I was thinking about removing that WARN together in this v5 patch, so there is less churn to touch the same function again. However, I am fine either way, so just shout out if you feel strongly towards a separate patch.

  reply	other threads:[~2020-01-17 15:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17  2:21 [PATCH -next v4] mm/hotplug: silence a lockdep splat with printk() Qian Cai
2020-01-17  2:49 ` Sergey Senozhatsky
2020-01-17  8:51 ` David Hildenbrand
2020-01-17  8:59   ` Michal Hocko
2020-01-17  9:25     ` David Hildenbrand
2020-01-17  9:40       ` Michal Hocko
2020-01-17  9:42         ` David Hildenbrand
2020-01-17 10:17           ` Michal Hocko
2020-01-17 10:18             ` David Hildenbrand
2020-01-17 12:40   ` Qian Cai
2020-01-17 12:53     ` David Hildenbrand
2020-01-17 13:30       ` Qian Cai
2020-01-17 13:42         ` David Hildenbrand
2020-01-17 14:42     ` Michal Hocko
2020-01-17 14:43       ` David Hildenbrand
2020-01-17 15:26         ` Michal Hocko
2020-01-17  8:59 ` Michal Hocko
2020-01-17 12:32   ` Qian Cai
2020-01-17 14:39     ` Michal Hocko
2020-01-17 15:05       ` Qian Cai [this message]
2020-01-17 15:46         ` Michal Hocko
2020-01-17 18:49           ` Qian Cai
2020-01-17 19:15             ` David Hildenbrand
2020-01-17 19:42               ` Qian Cai

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=3B7490FB-E915-4DC7-8739-01EDC023E22E@lca.pw \
    --to=cai@lca.pw \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky.work@gmail.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 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.