linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Anup Patel <anup@brainfault.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-riscv@lists.infradead.org
Subject: Re: [PATCH] riscv: remove free_initrd_mem
Date: Mon, 20 May 2019 13:34:12 +0530	[thread overview]
Message-ID: <CAAhSdy2XQ+mEMkrPOKSCwf+vZAdRE5SHp+PdDWALcyHudo7BxQ@mail.gmail.com> (raw)
In-Reply-To: <20190520063326.26083-1-hch@lst.de>

On Mon, May 20, 2019 at 12:04 PM Christoph Hellwig <hch@lst.de> wrote:
>
> The RISC-V free_initrd_mem is identical to the default one, except
> that it doesn't poison the freed memory.  Remove it so that the
> default implementations gets used instead.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  arch/riscv/mm/init.c | 5 -----
>  1 file changed, 5 deletions(-)
>
> diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
> index 8bf6f9c2d48c..b2341979d3eb 100644
> --- a/arch/riscv/mm/init.c
> +++ b/arch/riscv/mm/init.c
> @@ -92,11 +92,6 @@ static void __init setup_initrd(void)
>         initrd_start = 0;
>         initrd_end = 0;
>  }
> -
> -void __init free_initrd_mem(unsigned long start, unsigned long end)
> -{
> -       free_reserved_area((void *)start, (void *)end, -1, "initrd");
> -}
>  #endif /* CONFIG_BLK_DEV_INITRD */
>
>  void __init setup_bootmem(void)
> --
> 2.20.1
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv

LGTM.

Reviewed-by: Anup Patel <anup@brainfault.org>

Regards,
Anup

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2019-05-20  8:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20  6:33 [PATCH] riscv: remove free_initrd_mem Christoph Hellwig
2019-05-20  8:04 ` Anup Patel [this message]
2019-05-29 21:13 ` Palmer Dabbelt
2019-07-03 13:01   ` Christoph Hellwig
2019-07-04  9:51 ` Paul Walmsley

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=CAAhSdy2XQ+mEMkrPOKSCwf+vZAdRE5SHp+PdDWALcyHudo7BxQ@mail.gmail.com \
    --to=anup@brainfault.org \
    --cc=hch@lst.de \
    --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).