From: Dave Hansen <haveblue@us.ibm.com>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: "Luck, Tony" <tony.luck@intel.com>, Andi Kleen <ak@suse.de>,
"Tolentino, Matthew E" <matthew.e.tolentino@intel.com>,
linux-ia64@vger.kernel.org,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>,
x86-64 Discuss <discuss@x86-64.org>
Subject: Re: [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes
Date: Fri, 10 Feb 2006 16:26:47 +0000 [thread overview]
Message-ID: <1139588807.9209.71.camel@localhost.localdomain> (raw)
In-Reply-To: <20060210223757.C530.Y-GOTO@jp.fujitsu.com>
On Fri, 2006-02-10 at 23:20 +0900, Yasunori Goto wrote:
>
> -extern unsigned long __initdata nr_kernel_pages;
> -extern unsigned long __initdata nr_all_pages;
> +extern unsigned long __meminitdata nr_kernel_pages;
> +extern unsigned long __meminitdata nr_all_pages;
Can you separate out these trivial changes into separate patches?
> +extern int kswapd(void *);
> +int new_pgdat_init(int nid, unsigned long start_pfn, unsigned long
> nr_pages)
> +{
> + unsigned long zones_size[MAX_NR_ZONES] = {0};
> + unsigned long zholes_size[MAX_NR_ZONES] = {0};
> + unsigned long size = arch_pernode_size(nid);
> + pg_data_t *pgdat;
Whitespace borkage?
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: "Luck, Tony" <tony.luck@intel.com>, Andi Kleen <ak@suse.de>,
"Tolentino, Matthew E" <matthew.e.tolentino@intel.com>,
linux-ia64@vger.kernel.org,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>,
x86-64 Discuss <discuss@x86-64.org>
Subject: Re: [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat allocation)
Date: Fri, 10 Feb 2006 08:26:47 -0800 [thread overview]
Message-ID: <1139588807.9209.71.camel@localhost.localdomain> (raw)
In-Reply-To: <20060210223757.C530.Y-GOTO@jp.fujitsu.com>
On Fri, 2006-02-10 at 23:20 +0900, Yasunori Goto wrote:
>
> -extern unsigned long __initdata nr_kernel_pages;
> -extern unsigned long __initdata nr_all_pages;
> +extern unsigned long __meminitdata nr_kernel_pages;
> +extern unsigned long __meminitdata nr_all_pages;
Can you separate out these trivial changes into separate patches?
> +extern int kswapd(void *);
> +int new_pgdat_init(int nid, unsigned long start_pfn, unsigned long
> nr_pages)
> +{
> + unsigned long zones_size[MAX_NR_ZONES] = {0};
> + unsigned long zholes_size[MAX_NR_ZONES] = {0};
> + unsigned long size = arch_pernode_size(nid);
> + pg_data_t *pgdat;
Whitespace borkage?
-- Dave
next prev parent reply other threads:[~2006-02-10 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 14:20 [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat allocation) Yasunori Goto
2006-02-10 14:20 ` Yasunori Goto
2006-02-10 16:26 ` Dave Hansen [this message]
2006-02-10 16:26 ` [Lhms-devel] " Dave Hansen
2006-02-11 3:02 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat all Yasunori Goto
2006-02-11 3:02 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat allocation) Yasunori Goto
2006-02-10 16:28 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes Dave Hansen
2006-02-10 16:28 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat allocation) Dave Hansen
2006-02-11 3:06 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat all Yasunori Goto
2006-02-11 3:06 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat allocation) Yasunori Goto
2006-02-10 16:28 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes Dave Hansen
2006-02-10 16:28 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat allocation) Dave Hansen
2006-02-10 16:30 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes Dave Hansen
2006-02-10 16:30 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat allocation) Dave Hansen
2006-02-11 3:08 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat all Yasunori Goto
2006-02-11 3:08 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat allocation) Yasunori Goto
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=1139588807.9209.71.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=tony.luck@intel.com \
--cc=y-goto@jp.fujitsu.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.