From: Pavel Tatashin <pasha.tatashin@oracle.com>
To: osalvador@techadventures.net
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
iamjoonsoo.kim@lge.com, aaron.lu@intel.com,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
osalvador@suse.de
Subject: Re: [PATCH 1/3] mm/page_alloc: Move ifdefery out of free_area_init_core
Date: Thu, 19 Jul 2018 09:18:06 -0400 [thread overview]
Message-ID: <CAGM2reaQkRDYvMsH=nVa=ZZTwAcqEE=omn6ma3=y8N7=UX=65g@mail.gmail.com> (raw)
In-Reply-To: <20180719121902.GB8750@techadventures.net>
> + zone_set_nid(nid);
>
> This should be:
>
> zone_set_nid(zone, nid);
>
> I fixed it up in your patch, I hope that is ok.
Yes, thank you. I fixed this when compile tested this patch, but must
have forgotten to regenerate the patch before sending it.
Thank you,
Pavel
>
> Thanks
> --
> Oscar Salvador
> SUSE L3
>
next prev parent reply other threads:[~2018-07-19 13:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 12:47 [PATCH 0/3] Re-structure free_area_init_node / free_area_init_core osalvador
2018-07-18 12:47 ` [PATCH 1/3] mm/page_alloc: Move ifdefery out of free_area_init_core osalvador
2018-07-18 13:37 ` Michal Hocko
2018-07-18 14:11 ` Pavel Tatashin
2018-07-18 15:15 ` Oscar Salvador
2018-07-19 12:19 ` Oscar Salvador
2018-07-19 13:18 ` Pavel Tatashin [this message]
2018-07-18 12:47 ` [PATCH 2/3] mm/page_alloc: Refactor free_area_init_core osalvador
2018-07-18 13:36 ` Michal Hocko
2018-07-18 14:12 ` Oscar Salvador
2018-07-18 15:11 ` Oscar Salvador
2018-07-18 12:47 ` [PATCH 3/3] mm/page_alloc: Split context in free_area_init_node osalvador
2018-07-18 14:34 ` Pavel Tatashin
2018-07-19 7:35 ` Oscar Salvador
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='CAGM2reaQkRDYvMsH=nVa=ZZTwAcqEE=omn6ma3=y8N7=UX=65g@mail.gmail.com' \
--to=pasha.tatashin@oracle.com \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=osalvador@techadventures.net \
--cc=vbabka@suse.cz \
/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).