From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: CONFIG_ACPI_HOTPLUG_MEMORY=m with x86_64 devel tree Date: 22 Mar 2006 18:13:29 +0100 Message-ID: <20060322171329.GA30737@muc.de> References: <20060321222332.1a037c8e.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from colin.muc.de ([193.149.48.1]:42503 "EHLO mail.muc.de") by vger.kernel.org with ESMTP id S1750782AbWCVRNh (ORCPT ); Wed, 22 Mar 2006 12:13:37 -0500 Date: Wed, 22 Mar 2006 18:13:29 +0100 Content-Disposition: inline In-Reply-To: <20060321222332.1a037c8e.akpm@osdl.org> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Andrew Morton Cc: linux-acpi@vger.kernel.org On Tue, Mar 21, 2006 at 10:23:32PM -0800, Andrew Morton wrote: > WARNING: "remove_memory" [drivers/acpi/acpi_memhotplug.ko] undefined! > WARNING: "add_memory" [drivers/acpi/acpi_memhotplug.ko] undefined! > WARNING: "acpi_os_allocate" [drivers/acpi/acpi_memhotplug.ko] undefined! > > Does it actually make sense to load acpi_memhotplug.ko as a module? Will Yes. > it all work? Just need to export the symbols I think. Thanks for the headsup. -Andi