From: Mike Rapoport <rppt@linux.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
Palmer Dabbelt <palmer@sifive.com>,
Richard Kuo <rkuo@codeaurora.org>,
linux-arch@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-riscv@lists.infradead.org,
Mike Rapoport <rppt@linux.ibm.com>
Subject: [PATCH v2 2/4] hexagon: switch over to generic free_initmem()
Date: Mon, 18 Feb 2019 20:41:23 +0200 [thread overview]
Message-ID: <1550515285-17446-3-git-send-email-rppt@linux.ibm.com> (raw)
In-Reply-To: <1550515285-17446-1-git-send-email-rppt@linux.ibm.com>
hexagon implementation of free_initmem() is currently empty and marked with
comment
* Todo: free pages between __init_begin and __init_end; possibly
* some devtree related stuff as well.
Switch it to the generic implementation.
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
---
arch/hexagon/mm/init.c | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/arch/hexagon/mm/init.c b/arch/hexagon/mm/init.c
index 1719ede..41cf342 100644
--- a/arch/hexagon/mm/init.c
+++ b/arch/hexagon/mm/init.c
@@ -85,16 +85,6 @@ void __init mem_init(void)
}
/*
- * free_initmem - frees memory used by stuff declared with __init
- *
- * Todo: free pages between __init_begin and __init_end; possibly
- * some devtree related stuff as well.
- */
-void __ref free_initmem(void)
-{
-}
-
-/*
* free_initrd_mem - frees... initrd memory.
* @start - start of init memory
* @end - end of init memory
--
2.7.4
next prev parent reply other threads:[~2019-02-18 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 18:41 [PATCH v2 0/4] provide a generic free_initmem implementation Mike Rapoport
2019-02-18 18:41 ` [PATCH v2 1/4] init: " Mike Rapoport
2019-02-18 18:41 ` Mike Rapoport [this message]
2019-02-18 18:41 ` [PATCH v2 3/4] init: free_initmem: poison freed init memory Mike Rapoport
2019-02-18 18:41 ` [PATCH v2 4/4] riscv: switch over to generic free_initmem() Mike Rapoport
2019-03-25 7:20 ` [PATCH v2 0/4] provide a generic free_initmem implementation Mike Rapoport
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=1550515285-17446-3-git-send-email-rppt@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=rkuo@codeaurora.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).