[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1201886317.11808.32.camel@dyn9047017100.beaverton.ibm.com>
Date: Fri, 01 Feb 2008 09:18:37 -0800
From: Badari Pulavarty <pbadari@...ibm.com>
To: Jan-Bernd Themann <ossthema@...ibm.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Jan-Bernd Themann <themann@...ibm.com>,
Thomas Klein <osstklei@...ibm.com>,
Christoph Raisch <RAISCH@...ibm.com>,
Marcus Eder <meder@...ibm.com>,
netdev <netdev@...r.kernel.org>,
Stefan Roscher <stefan.roscher@...ibm.com>
Subject: Re: [PATCH] drivers/base: export (un)register_memory_notifier
On Fri, 2008-02-01 at 17:16 +0100, Jan-Bernd Themann wrote:
> Drivers like eHEA need memory notifiers in order to
> update their internal DMA memory map when memory is added
> to or removed from the system.
>
> Signed-off-by: Jan-Bernd Themann <themann@...ibm.com>
>
> ---
> Comment: eHEA patches that exploit these functions will follow
>
>
> drivers/base/memory.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
> index 7ae413f..1e1bd4c 100644
> --- a/drivers/base/memory.c
> +++ b/drivers/base/memory.c
> @@ -52,11 +52,13 @@ int register_memory_notifier(struct notifier_block *nb)
> {
> return blocking_notifier_chain_register(&memory_chain, nb);
> }
> +EXPORT_SYMBOL(register_memory_notifier);
>
> void unregister_memory_notifier(struct notifier_block *nb)
> {
> blocking_notifier_chain_unregister(&memory_chain, nb);
> }
> +EXPORT_SYMBOL(unregister_memory_notifier);
>
> /*
> * register_memory - Setup a sysfs device for a memory block
Is there a reason for not making them EXPORT_SYMBOL_GPL() ?
Otherwise, looks good to me.
I have been planning to send this as part of my next update
with ppc64 arch-specific remove support and generic __remove_pages()
support. If this is blocking your work, lets get this in.
Acked-by: Badari Pulavarty <pbadari@...ibm.com>
Thanks,
Badari
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists