linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rich Felker <dalias@libc.org>
To: linux-riscv@lists.infradead.org
Subject: Re: [PATCH v5 15/16] sh: Switch to generic free_initrd_mem.
Date: Thu, 29 Mar 2018 16:26:56 +0000	[thread overview]
Message-ID: <20180329162656.GP1436@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180329113207.30674-15-shea@shealevy.com>

On Thu, Mar 29, 2018 at 07:32:06AM -0400, Shea Levy wrote:
> The generic implementation is functionally identical.
> 
> Signed-off-by: Shea Levy <shea@shealevy.com>
> ---
>  arch/sh/mm/init.c | 7 -------
>  1 file changed, 7 deletions(-)
> 
> diff --git a/arch/sh/mm/init.c b/arch/sh/mm/init.c
> index ce0bbaa7e404..7451459d0725 100644
> --- a/arch/sh/mm/init.c
> +++ b/arch/sh/mm/init.c
> @@ -477,13 +477,6 @@ void free_initmem(void)
>  	free_initmem_default(-1);
>  }
>  
> -#ifdef CONFIG_BLK_DEV_INITRD
> -void free_initrd_mem(unsigned long start, unsigned long end)
> -{
> -	free_reserved_area((void *)start, (void *)end, -1, "initrd");
> -}
> -#endif
> -
>  #ifdef CONFIG_MEMORY_HOTPLUG
>  int arch_add_memory(int nid, u64 start, u64 size, struct vmem_altmap *altmap,
>  		bool want_memblock)
> -- 
> 2.16.2

LGTM.

Acked-by: Rich Felker <dalias@libc.org>

  reply	other threads:[~2018-03-29 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180328152714.6103-1-shea@shealevy.com>
     [not found] ` <20180328203659.18692-1-shea@shealevy.com>
2018-03-28 20:36   ` [PATCH v4 15/16] sh: Use generic free_initrd_mem Shea Levy
     [not found]   ` <20180329113207.30674-1-shea@shealevy.com>
2018-03-29 11:32     ` [PATCH v5 15/16] sh: Switch to " Shea Levy
2018-03-29 16:26       ` Rich Felker [this message]
     [not found]     ` <20180401145931.7932-1-shea@shealevy.com>
2018-04-01 14:59       ` [PATCH v6 " Shea Levy

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=20180329162656.GP1436@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).