From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 2/2] of: reserved_mem: Remove reserved regions count restriction
Date: Fri, 19 Nov 2021 11:56:08 +0200 [thread overview]
Message-ID: <YZd0uEWNH6Def3+8@smile.fi.intel.com> (raw)
In-Reply-To: <20211119075844.2902592-3-calvinzhang.cool@gmail.com>
On Fri, Nov 19, 2021 at 03:58:19PM +0800, Calvin Zhang wrote:
> Change to allocate reserved_mems dynamically. Static reserved regions
> must be reserved before any memblock allocations. The reserved_mems
> array couldn't be allocated until memblock and linear mapping are ready.
>
> So move the allocation and initialization of records and reserved memory
> from early_init_fdt_scan_reserved_mem() to of_reserved_mem_init().
> arch/arc/mm/init.c | 3 ++
> arch/arm/kernel/setup.c | 2 +
> arch/arm64/kernel/setup.c | 3 ++
> arch/csky/kernel/setup.c | 3 ++
> arch/h8300/kernel/setup.c | 2 +
> arch/mips/kernel/setup.c | 3 ++
> arch/nds32/kernel/setup.c | 3 ++
> arch/nios2/kernel/setup.c | 2 +
> arch/openrisc/kernel/setup.c | 3 ++
> arch/powerpc/kernel/setup-common.c | 3 ++
> arch/riscv/kernel/setup.c | 2 +
> arch/sh/kernel/setup.c | 3 ++
> arch/xtensa/kernel/setup.c | 2 +
Isn't x86 missed? Is it on purpose?
Would be nice to have this in the commit message or fixed accordingly.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-11-19 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 7:58 [OpenRISC] [PATCH 0/2] of: remove reserved regions count restriction Calvin Zhang
2021-11-19 7:58 ` [OpenRISC] [PATCH 1/2] of: Sort reserved_mem related code Calvin Zhang
2021-11-30 0:01 ` Rob Herring
2021-11-19 7:58 ` [OpenRISC] [PATCH 2/2] of: reserved_mem: Remove reserved regions count restriction Calvin Zhang
2021-11-19 9:56 ` Andy Shevchenko [this message]
2021-11-19 10:27 ` Calvin Zhang
2021-11-19 10:30 ` Calvin Zhang
2021-11-21 6:43 ` [OpenRISC] [PATCH 0/2] of: remove " Mike Rapoport
2021-11-21 9:01 ` Calvin Zhang
2021-11-30 0:08 ` Rob Herring
2021-11-30 21:07 ` 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=YZd0uEWNH6Def3+8@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=openrisc@lists.librecores.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