From: Catalin Marinas <catalin.marinas@arm.com>
To: Huacai Chen <chenhuacai@loongson.cn>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Huacai Chen <chenhuacai@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH] arm64: Use correct method to calculate nomap region boundaries
Date: Wed, 5 Jan 2022 18:20:16 +0000 [thread overview]
Message-ID: <164140680920.1009829.4040216260169936358.b4-ty@arm.com> (raw)
In-Reply-To: <20211022070646.41923-1-chenhuacai@loongson.cn>
On Fri, 22 Oct 2021 15:06:46 +0800, Huacai Chen wrote:
> Nomap regions are treated as "reserved". When region boundaries are not
> page aligned, we usually increase the "reserved" regions rather than
> decrease them. So, we should use memblock_region_reserved_base_pfn()/
> memblock_region_reserved_end_pfn() instead of memblock_region_memory_
> base_pfn()/memblock_region_memory_base_pfn() to calculate boundaries.
>
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64: Use correct method to calculate nomap region boundaries
https://git.kernel.org/arm64/c/daa149dd8cd4
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-01-05 18:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 7:06 [PATCH] arm64: Use correct method to calculate nomap region boundaries Huacai Chen
2021-10-27 8:35 ` Huacai Chen
2021-11-01 1:53 ` Guo Ren
2021-11-07 10:10 ` Huacai Chen
2021-12-02 10:08 ` Will Deacon
2021-12-06 4:46 ` Huacai Chen
2021-12-13 19:07 ` Will Deacon
2021-12-14 0:50 ` Huacai Chen
2021-12-14 14:11 ` Will Deacon
2021-12-15 0:31 ` Huacai Chen
2022-01-05 18:20 ` Catalin Marinas [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=164140680920.1009829.4040216260169936358.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=arnd@arndb.de \
--cc=chenhuacai@gmail.com \
--cc=chenhuacai@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.