From: Tang Chen <tangchen@cn.fujitsu.com>
To: Fabian Frederick <fabf@skynet.be>
Cc: <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] include/linux/memblock.h: add __init to memblock_set_bottom_up
Date: Mon, 9 Jun 2014 09:19:14 +0800 [thread overview]
Message-ID: <53950B92.6040504@cn.fujitsu.com> (raw)
In-Reply-To: <1402122084-25496-1-git-send-email-fabf@skynet.be>
Seeing from the code, it is OK.
Reviewed-by: Tang Chen<tangchen@cn.fujitsu.com>
Thanks.
On 06/07/2014 02:21 PM, Fabian Frederick wrote:
> memblock_set_bottom_up is only called by
> __init cmdline_parse_movable_node and __init numa_init.
>
> Cc: Andrew Morton<akpm@linux-foundation.org>
> Cc: Tang Chen<tangchen@cn.fujitsu.com>
> Signed-off-by: Fabian Frederick<fabf@skynet.be>
> ---
> This is untested.
>
> include/linux/memblock.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/memblock.h b/include/linux/memblock.h
> index 8a20a51..4d6dfcf 100644
> --- a/include/linux/memblock.h
> +++ b/include/linux/memblock.h
> @@ -198,7 +198,7 @@ phys_addr_t memblock_alloc(phys_addr_t size, phys_addr_t align);
> /*
> * Set the allocation direction to bottom-up or top-down.
> */
> -static inline void memblock_set_bottom_up(bool enable)
> +static inline void __init memblock_set_bottom_up(bool enable)
> {
> memblock.bottom_up = enable;
> }
> @@ -213,7 +213,7 @@ static inline bool memblock_bottom_up(void)
> return memblock.bottom_up;
> }
> #else
> -static inline void memblock_set_bottom_up(bool enable) {}
> +static inline void __init memblock_set_bottom_up(bool enable) {}
> static inline bool memblock_bottom_up(void) { return false; }
> #endif
>
prev parent reply other threads:[~2014-06-09 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 6:21 [PATCH 1/1] include/linux/memblock.h: add __init to memblock_set_bottom_up Fabian Frederick
2014-06-09 1:19 ` Tang Chen [this message]
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=53950B92.6040504@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=linux-kernel@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