From: Johannes Weiner <hannes@saeurebad.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jan Beulich <jbeulich@novell.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Propagate new nonpanic bootmem macros to CONFIG_HAVE_ARCH_BOOTMEM_NODE
Date: Wed, 13 Aug 2008 11:07:41 +0200 [thread overview]
Message-ID: <87k5el9tb6.fsf@skyscraper.fehenstaub.lan> (raw)
In-Reply-To: <20080813085509.GC23417@elte.hu> (Ingo Molnar's message of "Wed, 13 Aug 2008 10:55:09 +0200")
Hi Ingo,
Ingo Molnar <mingo@elte.hu> writes:
> * Jan Beulich <jbeulich@novell.com> wrote:
>
>> Sorry for not noticing this:
>> Acked-by: Jan Beulich <jbeulich@novell.com>
>>
>> >>> Johannes Weiner <hannes@saeurebad.de> 13.08.08 10:17 >>>
>> Commit 74768ed833344b "page allocator: use no-panic variant of
>> alloc_bootmem() in alloc_large_system_hash()" introduced two new
>> _nopanic macros which are undefined for CONFIG_HAVE_ARCH_BOOTMEM_NODE.
>>
>> Signed-off-by: Johannes Weiner <hannes@saeurebad.de>
>
> btw., i dont think the fix is complete, a quick grep shows:
>
> arch/avr32/Kconfig:config HAVE_ARCH_BOOTMEM_NODE
Uhm, I think a fix for that would be removing the knob from the avr32
Kconfig. It defaults to n and I couldn't find a place where this gets
enabled.
Furthermore, there doesn't seem to be any arch-specific code associated
with it (grep -R ARCH_BOOTMEM_NODE arch/avr32).
Hannes
next prev parent reply other threads:[~2008-08-13 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 13:35 [PATCH] use no-panic variant of alloc_bootmem() in alloc_large_system_hash() Jan Beulich
2008-08-13 8:17 ` [PATCH] Propagate new nonpanic bootmem macros to CONFIG_HAVE_ARCH_BOOTMEM_NODE Johannes Weiner
2008-08-13 8:30 ` Jan Beulich
2008-08-13 8:55 ` Ingo Molnar
2008-08-13 9:07 ` Johannes Weiner [this message]
2008-08-13 9:17 ` Ingo Molnar
2008-08-13 8:48 ` Ingo Molnar
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=87k5el9tb6.fsf@skyscraper.fehenstaub.lan \
--to=hannes@saeurebad.de \
--cc=dhowells@redhat.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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 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.