Linux ACPI
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: CONFIG_ACPI_HOTPLUG_MEMORY=m with x86_64 devel tree
Date: 22 Mar 2006 18:13:29 +0100
Date: Wed, 22 Mar 2006 18:13:29 +0100	[thread overview]
Message-ID: <20060322171329.GA30737@muc.de> (raw)
In-Reply-To: <20060321222332.1a037c8e.akpm@osdl.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


  parent reply	other threads:[~2006-03-22 17:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22  6:23 CONFIG_ACPI_HOTPLUG_MEMORY=m with x86_64 devel tree Andrew Morton
2006-03-22 10:56 ` Yasunori Goto
2006-03-22 11:02   ` Andrew Morton
2006-03-22 11:32     ` KAMEZAWA Hiroyuki
2006-03-22 19:21       ` Andi Kleen
2006-03-22 23:27         ` KAMEZAWA Hiroyuki
2006-03-23  0:07           ` Andi Kleen
2006-03-23  0:36             ` KAMEZAWA Hiroyuki
2006-03-23  2:43               ` Andi Kleen
2006-03-23  2:55                 ` KAMEZAWA Hiroyuki
2006-03-23  3:22                 ` KAMEZAWA Hiroyuki
2006-03-23 15:37                   ` Andi Kleen
2006-03-23  3:59                 ` KAMEZAWA Hiroyuki
2006-03-30 13:41                   ` CONFIG_ACPI_HOTPLUG_MEMORY=m with x86_64 devel tree II Andi Kleen
2006-03-30 13:54                     ` KAMEZAWA Hiroyuki
2006-03-30 14:18                       ` Andi Kleen
2006-03-30 14:25                         ` KAMEZAWA Hiroyuki
2006-03-30 14:31                           ` Andi Kleen
2006-03-22 17:13 ` Andi Kleen [this message]
2006-03-22 19:23 ` CONFIG_ACPI_HOTPLUG_MEMORY=m with x86_64 devel tree Andi Kleen

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=20060322171329.GA30737@muc.de \
    --to=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=linux-acpi@vger.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