From: Nathan Lynch <ntl@pobox.com>
To: Paul Mackerras <paulus@samba.org>
Cc: tklein@de.ibm.com, Jeff Garzik <jeff@garzik.org>,
themann@de.ibm.com,
Hannes Hering <hannes.hering@linux.vnet.ibm.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ossrosch@linux.vnet.ibm.com, linuxppc-dev@ozlabs.org,
raisch@de.ibm.com, Badari Pulavarty <pbadari@us.ibm.com>,
ossthema@de.ibm.com
Subject: Re: [PATCH 1/2] make walk_memory_resource available with MEMORY_HOTPLUG=n
Date: Fri, 6 Jun 2008 18:06:38 -0500 [thread overview]
Message-ID: <20080606230638.GC6638@localdomain> (raw)
In-Reply-To: <20080603223054.GC7475@localdomain>
Nathan Lynch wrote:
> The ehea driver was recently changed[1] to use walk_memory_resource() to
> detect the system's memory layout. However, walk_memory_resource() is
> available only when memory hotplug is enabled. So CONFIG_EHEA was
> made to depend on MEMORY_HOTPLUG [2], but it is inappropriate for a
> network driver to have such a dependency.
>
> Make the declaration of walk_memory_resource() and its powerpc
> implementation (ehea is powerpc-specific) unconditionally available.
Paul, can you take these two patches, or should I send them to akpm?
next prev parent reply other threads:[~2008-06-06 23:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 12:43 [PATCH 2/3] [2.6.26] ehea: Add dependency to Kconfig Hannes Hering
2008-05-28 16:44 ` Nathan Lynch
2008-06-03 8:07 ` Hannes Hering
2008-06-03 20:49 ` Nathan Lynch
2008-06-03 21:08 ` Badari Pulavarty
2008-06-03 21:11 ` Jeff Garzik
2008-06-03 22:30 ` [PATCH 1/2] make walk_memory_resource available with MEMORY_HOTPLUG=n Nathan Lynch
2008-06-06 19:43 ` Badari Pulavarty
2008-06-06 23:06 ` Nathan Lynch [this message]
2008-06-07 5:48 ` Paul Mackerras
2008-06-03 22:31 ` [PATCH 2/2] ehea: remove dependency on MEMORY_HOTPLUG Nathan Lynch
2008-06-03 22:42 ` Jeff Garzik
2008-06-04 5:27 ` Yasunori Goto
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=20080606230638.GC6638@localdomain \
--to=ntl@pobox.com \
--cc=hannes.hering@linux.vnet.ibm.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=ossrosch@linux.vnet.ibm.com \
--cc=ossthema@de.ibm.com \
--cc=paulus@samba.org \
--cc=pbadari@us.ibm.com \
--cc=raisch@de.ibm.com \
--cc=themann@de.ibm.com \
--cc=tklein@de.ibm.com \
/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).