From: Yinghai Lu <yinghai@kernel.org>
To: Tejun Heo <tj@kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: drop obsolete ARCH_BOOTMEM support
Date: Wed, 11 Apr 2012 10:03:50 -0700 [thread overview]
Message-ID: <CAE9FiQVmyTSUGKmusrVvj-38URhRFzvjv7w-2ch928kEiJPOhg@mail.gmail.com> (raw)
In-Reply-To: <20120411163016.GC12887@google.com>
On Wed, Apr 11, 2012 at 9:30 AM, Tejun Heo <tj@kernel.org> wrote:
> On Fri, Apr 06, 2012 at 02:47:35PM +0200, Sam Ravnborg wrote:
>> From ae6cdc767f973f39cb205af4b80ff13f35a1b66e Mon Sep 17 00:00:00 2001
>> From: Sam Ravnborg <sam@ravnborg.org>
>> Date: Fri, 6 Apr 2012 13:37:08 +0200
>> Subject: [PATCH] x86: drop obsolete ARCH_BOOTMEM support
>>
>> x86 unconditionally uses NO_BOOTMEM so there is no use
>> of the HAVE_ARCH_BOOTMEM support as mm/bootmem.c is the
>> only file referencing this symbol.
>>
>> bootmem_arch_preferred_node() is the function referred
>> in the mm/bootmem.c code and can thuis be dropped too.
>>
>> x86 was the sole user of HAVE_ARCH_BOOTMEM - so there is
>> an opportunity to clean up a little in mm/bootmem.c too
>> if we do not expect other users to emerge.
>
> avr32 seems to have it too?
avr32 is:
config HAVE_ARCH_BOOTMEM
def_bool n
so that is not used with avr32
Yinghai
next prev parent reply other threads:[~2012-04-11 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 12:47 [PATCH] x86: drop obsolete ARCH_BOOTMEM support Sam Ravnborg
2012-04-11 16:30 ` Tejun Heo
2012-04-11 17:03 ` Yinghai Lu [this message]
2012-04-11 17:11 ` Tejun Heo
2012-04-11 20:53 ` Sam Ravnborg
2012-04-14 18:26 ` [tip:x86/mm] x86: Drop " tip-bot for Sam Ravnborg
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=CAE9FiQVmyTSUGKmusrVvj-38URhRFzvjv7w-2ch928kEiJPOhg@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--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 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.