From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Tejun Heo <tj@kernel.org>, Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH] bootmem.c: Avoid c90 declaration warning
Date: Thu, 18 Jun 2009 13:24:10 -0700 [thread overview]
Message-ID: <20090618132410.0b55cd90.akpm@linux-foundation.org> (raw)
In-Reply-To: <1245355633.29927.16.camel@Joe-Laptop.home>
On Thu, 18 Jun 2009 13:07:13 -0700
Joe Perches <joe@perches.com> wrote:
> Signed-off-by: Joe Perches <joe@perches.com>
>
> diff --git a/mm/bootmem.c b/mm/bootmem.c
> index 282df0a..09d9c98 100644
> --- a/mm/bootmem.c
> +++ b/mm/bootmem.c
> @@ -536,11 +536,13 @@ static void * __init alloc_arch_preferred_bootmem(bootmem_data_t *bdata,
> return kzalloc(size, GFP_NOWAIT);
>
> #ifdef CONFIG_HAVE_ARCH_BOOTMEM
> + {
> bootmem_data_t *p_bdata;
>
> p_bdata = bootmem_arch_preferred_node(bdata, size, align, goal, limit);
> if (p_bdata)
> return alloc_bootmem_core(p_bdata, size, align, goal, limit);
> + }
> #endif
> return NULL;
> }
Well yes.
We'll be needing some tabs there.
Unrelatedly, I'm struggling a bit with bootmem_arch_preferred_node().
It's only defined if CONFIG_X86_32=y && CONFIG_NEED_MULTIPLE_NODES=y,
but it gets called if CONFIG_HAVE_ARCH_BOOTMEM=y.
Is this correct, logical and as simple as we can make it??
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-06-18 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 20:07 [PATCH] bootmem.c: Avoid c90 declaration warning Joe Perches
2009-06-18 20:24 ` Andrew Morton [this message]
2009-06-18 21:57 ` Johannes Weiner
2009-06-19 0:26 ` Yinghai Lu
2009-06-19 16:43 ` Johannes Weiner
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=20090618132410.0b55cd90.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=hannes@cmpxchg.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
--cc=tj@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).