linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: linux-mm@kvack.org
Cc: Tony Luck <tony.luck@intel.com>,
	linux-ia64@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Pingfan Liu <kernelfans@gmail.com>,
	Dave Hansen <dave.hansen@intel.com>, Ingo Molnar <mingo@elte.hu>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/2] x86, numa: always initialize all possible nodes
Date: Mon, 15 Apr 2019 13:42:09 +0200	[thread overview]
Message-ID: <20190415114209.GJ3366@dhcp22.suse.cz> (raw)
In-Reply-To: <20190226131201.GA10588@dhcp22.suse.cz>

On Tue 26-02-19 14:12:01, Michal Hocko wrote:
> On Tue 12-02-19 10:53:41, Michal Hocko wrote:
> > Hi,
> > this has been posted as an RFC previously [1]. There didn't seem to be
> > any objections so I am reposting this for inclusion. I have added a
> > debugging patch which prints the zonelist setup for each numa node
> > for an easier debugging of a broken zonelist setup.
> > 
> > [1] http://lkml.kernel.org/r/20190114082416.30939-1-mhocko@kernel.org
> 
> Friendly ping. I haven't heard any complains so can we route this via
> tip/x86/mm or should we go via mmotm.

It seems that Dave is busy. Let's add Andrew. Can we get this [1] merged
finally, please?

[1] http://lkml.kernel.org/r/20190212095343.23315-1-mhocko@kernel.org
-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2019-04-15 11:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12  9:53 [PATCH 0/2] x86, numa: always initialize all possible nodes Michal Hocko
2019-02-12  9:53 ` [PATCH 1/2] " Michal Hocko
2019-05-01 19:12   ` Barret Rhoden
2019-05-02 13:00     ` Michal Hocko
2019-06-26 13:54       ` Michal Hocko
2019-02-12  9:53 ` [PATCH 2/2] mm: be more verbose about zonelist initialization Michal Hocko
2019-02-13  0:12   ` kbuild test robot
2019-02-13  2:13   ` kbuild test robot
2019-02-13  9:40   ` [PATCH v2 " Michal Hocko
2019-02-13  9:43   ` [PATCH v3 " Michal Hocko
2019-02-13 10:32     ` Peter Zijlstra
2019-02-13 11:50       ` Michal Hocko
2019-02-13 13:11         ` Peter Zijlstra
2019-02-13 13:41           ` Michal Hocko
2019-02-13 16:14     ` Dave Hansen
2019-02-13 16:18       ` Michal Hocko
2019-02-12 10:19 ` [PATCH 0/2] x86, numa: always initialize all possible nodes Mike Rapoport
2019-02-26 13:12 ` Michal Hocko
2019-04-15 11:42   ` Michal Hocko [this message]
2019-04-15 15:43     ` Dave Hansen
2019-04-16  6:54     ` Michal Hocko

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=20190415114209.GJ3366@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=dave.hansen@intel.com \
    --cc=kernelfans@gmail.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tony.luck@intel.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).