From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, rientjes@google.com,
linuxram@us.ibm.com, guz.fnst@cn.fujitsu.com, tmac@hp.com,
wency@cn.fujitsu.com, tangchen@cn.fujitsu.com,
jiang.liu@huawei.com
Subject: Re: [PATCH] resource: Update config option of release_mem_region_adjustable()
Date: Fri, 12 Apr 2013 08:50:08 +0900 [thread overview]
Message-ID: <51674C30.5060309@jp.fujitsu.com> (raw)
In-Reply-To: <1365719185-4799-1-git-send-email-toshi.kani@hp.com>
2013/04/12 7:26, Toshi Kani wrote:
> Changed the config option of release_mem_region_adjustable() from
> CONFIG_MEMORY_HOTPLUG to CONFIG_MEMORY_HOTREMOVE since this function
> is only used for memory hot-delete.
>
> Signed-off-by: Toshi Kani <toshi.kani@hp.com>
Reviewed-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Thanks,
Yasuaki Ishimatsu
> ---
>
> This patch applies on top of the two patches below:
> Re: [PATCH v3 2/3] resource: Add release_mem_region_adjustable()
> https://lkml.org/lkml/2013/4/11/381
> [patch] mm, hotplug: avoid compiling memory hotremove functions when disabled
> https://lkml.org/lkml/2013/4/10/37
>
> ---
> include/linux/ioport.h | 2 +-
> kernel/resource.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/ioport.h b/include/linux/ioport.h
> index 961d4dc..89b7c24 100644
> --- a/include/linux/ioport.h
> +++ b/include/linux/ioport.h
> @@ -192,7 +192,7 @@ extern struct resource * __request_region(struct resource *,
> extern int __check_region(struct resource *, resource_size_t, resource_size_t);
> extern void __release_region(struct resource *, resource_size_t,
> resource_size_t);
> -#ifdef CONFIG_MEMORY_HOTPLUG
> +#ifdef CONFIG_MEMORY_HOTREMOVE
> extern int release_mem_region_adjustable(struct resource *, resource_size_t,
> resource_size_t);
> #endif
> diff --git a/kernel/resource.c b/kernel/resource.c
> index 16bfd39..4aef886 100644
> --- a/kernel/resource.c
> +++ b/kernel/resource.c
> @@ -1021,7 +1021,7 @@ void __release_region(struct resource *parent, resource_size_t start,
> }
> EXPORT_SYMBOL(__release_region);
>
> -#ifdef CONFIG_MEMORY_HOTPLUG
> +#ifdef CONFIG_MEMORY_HOTREMOVE
> /**
> * release_mem_region_adjustable - release a previously reserved memory region
> * @parent: parent resource descriptor
> @@ -1122,7 +1122,7 @@ int release_mem_region_adjustable(struct resource *parent,
> kfree(new_res);
> return ret;
> }
> -#endif /* CONFIG_MEMORY_HOTPLUG */
> +#endif /* CONFIG_MEMORY_HOTREMOVE */
>
> /*
> * Managed region resource
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-04-11 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 22:26 Toshi Kani
2013-04-11 22:40 ` David Rientjes
2013-04-11 22:31 ` Toshi Kani
2013-04-11 23:50 ` Yasuaki Ishimatsu [this message]
2013-04-11 23:43 ` Toshi Kani
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=51674C30.5060309@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=guz.fnst@cn.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxram@us.ibm.com \
--cc=rientjes@google.com \
--cc=tangchen@cn.fujitsu.com \
--cc=tmac@hp.com \
--cc=toshi.kani@hp.com \
--cc=wency@cn.fujitsu.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