All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Baoquan He <bhe@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
	Balbir Singh <bsingharora@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	jgross@suse.com, akpm@linux-foundation.org
Subject: Re: [Patch v2] mm/hotplug: Only respect mem= parameter during boot stage
Date: Tue, 10 Dec 2019 11:21:55 +0100	[thread overview]
Message-ID: <20191210102155.GD10404@dhcp22.suse.cz> (raw)
In-Reply-To: <20191210101100.GM2984@MiWiFi-R3L-srv>

On Tue 10-12-19 18:11:00, Baoquan He wrote:
> On 12/10/19 at 10:50am, Michal Hocko wrote:
[...]
> > [1] Btw. it would have been much better if you posted the version 2 only
> > after all the feedback got discussed properly.
> 
> You could have replied to wrong person. 
> 
> I don't know the use case David told. My motivation was to make memory hotplug
> not impacted after boot. I thought I have got your question and answered
> it. I will wait a little longer when post next time.

let me reply to your original email.
-- 
Michal Hocko
SUSE Labs


  reply	other threads:[~2019-12-10 10:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  8:44 [Patch v2] mm/hotplug: Only respect mem= parameter during boot stage Baoquan He
2019-12-10  9:07 ` Jürgen Groß
2019-12-10  9:24 ` Balbir Singh
2019-12-10  9:34   ` Baoquan He
2019-12-10  9:36   ` David Hildenbrand
2019-12-10  9:37     ` David Hildenbrand
2019-12-10  9:41       ` Balbir Singh
2019-12-10  9:50     ` Michal Hocko
2019-12-10 10:11       ` Baoquan He
2019-12-10 10:21         ` Michal Hocko [this message]
2019-12-10  9:32 ` David Hildenbrand

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=20191210102155.GD10404@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=bsingharora@gmail.com \
    --cc=david@redhat.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 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.