From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Youling Tang <tangyouling@loongson.cn>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Remove unused BOOT_MEM_INIT_RAM
Date: Mon, 14 Sep 2020 13:08:56 +0200 [thread overview]
Message-ID: <20200914110856.GA8974@alpha.franken.de> (raw)
In-Reply-To: <06109011-21af-ad1d-41cb-18542b9b77f6@loongson.cn>
On Mon, Sep 14, 2020 at 06:39:51PM +0800, Youling Tang wrote:
>
>
> On 09/14/2020 12:32 PM, Jiaxun Yang wrote:
> >
> >
> >在 2020/9/12 9:59, Youling Tang 写道:
> >>Commit a94e4f24ec83 ("MIPS: init: Drop boot_mem_map") left
> >>the BOOT_MEM_INIT_RAM unused, remove it.
> >>
> >>Signed-off-by: Youling Tang <tangyouling@loongson.cn>
> >>---
> >> arch/mips/include/asm/bootinfo.h | 1 -
> >> 1 file changed, 1 deletion(-)
> >>
> >>diff --git a/arch/mips/include/asm/bootinfo.h
> >>b/arch/mips/include/asm/bootinfo.h
> >>index 147c932..39196ae 100644
> >>--- a/arch/mips/include/asm/bootinfo.h
> >>+++ b/arch/mips/include/asm/bootinfo.h
> >>@@ -91,7 +91,6 @@ extern unsigned long mips_machtype;
> >> #define BOOT_MEM_RAM 1
> >> #define BOOT_MEM_ROM_DATA 2
> >> #define BOOT_MEM_RESERVED 3
> >>-#define BOOT_MEM_INIT_RAM 4
> >
> >If you're willing to remove that you'd better turn the memtype struct
> >into a enum.
> >
> Hi Jiaxun,
> Do you mean to modify it as follows?
>
> enum boot_memtype {
> BOOT_MEM_RAM,
> BOOT_MEM_ROM_DATA,
> BOOT_MEM_RESERVED,
> BOOT_MEM_NOMAP,
> };
that's not worth the effort, we should convert from add_memory_region
to direct memblock_XXX calls and get rid of MIPS boot mem completely.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-09-14 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 1:59 Youling Tang
2020-09-14 4:32 ` Jiaxun Yang
2020-09-14 10:39 ` Youling Tang
2020-09-14 11:08 ` Thomas Bogendoerfer [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=20200914110856.GA8974@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tangyouling@loongson.cn \
/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
all inboxes | Powered by JetHome®