From: Alexander Sverdlin <alexander.sverdlin@nokia.com>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Serge Semin <fancer.lancer@gmail.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, Paul Burton <paulburton@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: reserve the memblock right after the kernel
Date: Fri, 13 Nov 2020 13:29:06 +0100 [thread overview]
Message-ID: <9d8c55a2-4c8b-8cb0-0c3d-004554e14ef3@nokia.com> (raw)
In-Reply-To: <4625868b-f845-2f03-c3f2-fc3ff1ccf63d@flygoat.com>
Hi!
On 13/11/2020 03:30, Jiaxun Yang wrote:
>> 2) The check_kernel_sections_mem() method can be removed. But it
>> should be done carefully. We at least need to try to find all the
>> platforms, which rely on its functionality.
> It have been more than 10 years since introducing this this check, but
> I believe there must be a reason at the time.
It doesn't look like 10 years to me :)
commit a94e4f24ec836c8984f839594bad7454184975b1
Author: Jiaxun Yang <jiaxun.yang@flygoat.com>
Date: Mon Aug 19 22:23:13 2019 +0800
MIPS: init: Drop boot_mem_map
at least not so long in public, that's why we only noticed recently, that
is breaks Octeon platform.
--
Best regards,
Alexander Sverdlin.
next prev parent reply other threads:[~2020-11-13 12:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 14:10 [PATCH] MIPS: reserve the memblock right after the kernel Alexander A Sverdlin
2020-11-07 9:40 ` Thomas Bogendoerfer
2020-11-09 10:34 ` Alexander Sverdlin
2020-11-09 11:08 ` Alexander Sverdlin
2020-11-10 9:55 ` Thomas Bogendoerfer
2020-11-10 10:29 ` Alexander Sverdlin
2020-11-11 14:52 ` Serge Semin
2020-11-13 2:30 ` Jiaxun Yang
2020-11-13 3:28 ` Jinyang He
2020-11-13 3:49 ` Maciej W. Rozycki
2020-11-13 12:29 ` Alexander Sverdlin [this message]
2020-11-13 12:56 ` Alexander Sverdlin
2020-11-13 9:17 ` Alexander Sverdlin
2020-11-13 13:09 ` Alexander Sverdlin
2020-11-16 22:31 ` Serge Semin
2020-11-17 9:41 ` Alexander Sverdlin
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=9d8c55a2-4c8b-8cb0-0c3d-004554e14ef3@nokia.com \
--to=alexander.sverdlin@nokia.com \
--cc=fancer.lancer@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).