From: Mel Gorman <mgorman@suse.de>
To: "Alex Ng (LIS)" <alexng@microsoft.com>
Cc: Waiman Long <waiman.long@hp.com>,
Robin Holt <robinmholt@gmail.com>, Nate Zimmer <nzimmer@sgi.com>,
Dave Hansen <dave.hansen@intel.com>,
Scott Norton <scott.norton@hp.com>,
"Luck, Tony" <tony.luck@intel.com>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regarding patch "mm: meminit: make __early_pfn_to_nid SMP-safe and introduce meminit_pfn_in_nid"
Date: Thu, 16 Jul 2015 13:47:59 +0100 [thread overview]
Message-ID: <20150716124758.GA2561@suse.de> (raw)
In-Reply-To: <BY2PR0301MB1655CB50F3539863FF5DC252D89A0@BY2PR0301MB1655.namprd03.prod.outlook.com>
On Wed, Jul 15, 2015 at 10:45:11PM +0000, Alex Ng (LIS) wrote:
> > Agreed. Lets hear first if it addresses Alex problem first and if so,
> > I'll apply your feedback and put a changelog on it. There are now at least
> > three follow-on patches that I'm waiting for feedback on.
> >
> > --
> > Mel Gorman
> > SUSE Labs
>
> Tried this patch and it addresses the hotplug issue. It's no longer crashing.
>
Excellent, thanks for that Alex. I've taken the liberty of adding the
following.
Reported-and-tested-by: Alex Ng <alexng@microsoft.com>
I'm hoping to get feedback on another two meminit patch and do all the
fixes at once but if it's still quiet tomorrow then I'll send them all on
to Andrew.
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2015-07-16 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BY2PR0301MB1655C1BB6C4CBE0AD6B9E9D8D89A0@BY2PR0301MB1655.namprd03.prod.outlook.com>
[not found] ` <20150715134009.GD6812@suse.de>
[not found] ` <55A66904.2080008@hp.com>
[not found] ` <20150715145041.GE6812@suse.de>
2015-07-15 22:45 ` Regarding patch "mm: meminit: make __early_pfn_to_nid SMP-safe and introduce meminit_pfn_in_nid" Alex Ng (LIS)
2015-07-16 12:47 ` Mel Gorman [this message]
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=20150716124758.GA2561@suse.de \
--to=mgorman@suse.de \
--cc=alexng@microsoft.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nzimmer@sgi.com \
--cc=robinmholt@gmail.com \
--cc=scott.norton@hp.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=waiman.long@hp.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.