From: David Hildenbrand <david@redhat.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
catalin.marinas@arm.com, will@kernel.org, rppt@kernel.org
Cc: akpm@linux-foundation.org, anshuman.khandual@arm.com,
geert+renesas@glider.be, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 1/2] arm64: mm: apply __ro_after_init to memory_limit
Date: Wed, 15 Dec 2021 11:02:26 +0100 [thread overview]
Message-ID: <bbdc65e7-2028-4314-3174-c25a9e2d7c62@redhat.com> (raw)
In-Reply-To: <20211215064559.2843555-1-peng.fan@oss.nxp.com>
On 15.12.21 07:45, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> This variable is only set during initialization, so mark with
> __ro_after_init.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> arch/arm64/mm/init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index a8834434af99..db63cc885771 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -172,7 +172,7 @@ int pfn_is_map_memory(unsigned long pfn)
> }
> EXPORT_SYMBOL(pfn_is_map_memory);
>
> -static phys_addr_t memory_limit = PHYS_ADDR_MAX;
> +static phys_addr_t memory_limit __ro_after_init = PHYS_ADDR_MAX;
>
> /*
> * Limit the memory size that was specified via FDT.
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-12-15 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 6:45 Peng Fan (OSS)
2021-12-15 6:45 ` [PATCH 2/2] arm64: mm: support bootparam max_addr Peng Fan (OSS)
2021-12-15 7:32 ` Ard Biesheuvel
2021-12-15 7:59 ` Peng Fan
2021-12-15 9:24 ` Mike Rapoport
2021-12-15 9:30 ` Peng Fan
2021-12-15 9:53 ` Mike Rapoport
2021-12-15 12:05 ` Peng Fan
2021-12-16 14:19 ` Mike Rapoport
2021-12-15 7:30 ` [PATCH 1/2] arm64: mm: apply __ro_after_init to memory_limit Ard Biesheuvel
2021-12-15 10:02 ` David Hildenbrand [this message]
2022-01-20 15:56 ` (subset) " Catalin Marinas
2022-01-21 2:28 ` Anshuman Khandual
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=bbdc65e7-2028-4314-3174-c25a9e2d7c62@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=rppt@kernel.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 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®