From: "Orzel, Michal" <michal.orzel@amd.com>
To: Ayan Kumar Halder <ayan.kumar.halder@amd.com>,
xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH v2 1/4] xen/arm32: Initialize MM specific registers in enable_mmu
Date: Mon, 17 Mar 2025 12:40:19 +0100 [thread overview]
Message-ID: <cd2526bd-9dfe-4c74-8083-0bdbadc42ec6@amd.com> (raw)
In-Reply-To: <20250313182850.1527052-2-ayan.kumar.halder@amd.com>
On 13/03/2025 19:28, Ayan Kumar Halder wrote:
> All the memory management specific registers are initialized in enable_mmu.
The title is a bit misleading (description does not help too). It's a pure code
movement, yet it's not mentioned at all. This can be fixed by changing title:
"Move MM specific registers to enable_mmu"
>
> Signed-off-by: Ayan Kumar Halder <ayan.kumar.halder@amd.com>
With the title changed:
Reviewed-by: Michal Orzel <michal.orzel@amd.com>
~Michal
next prev parent reply other threads:[~2025-03-17 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 18:28 [PATCH v2 0/4] Enable early bootup of Armv8-R AArch32 systems Ayan Kumar Halder
2025-03-13 18:28 ` [PATCH v2 1/4] xen/arm32: Initialize MM specific registers in enable_mmu Ayan Kumar Halder
2025-03-17 11:40 ` Orzel, Michal [this message]
2025-03-19 11:48 ` Ayan Kumar Halder
2025-03-13 18:28 ` [PATCH v2 2/4] xen/arm32: mpu: Create boot-time MPU protection regions Ayan Kumar Halder
2025-03-17 11:56 ` Orzel, Michal
2025-03-13 18:28 ` [PATCH v2 3/4] xen/arm32: mpu: Implement a dummy enable_secondary_cpu_mm Ayan Kumar Halder
2025-03-13 18:28 ` [PATCH v2 4/4] xen/arm32: Allow ARM_PA_BITS_40 only if !MPU Ayan Kumar Halder
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=cd2526bd-9dfe-4c74-8083-0bdbadc42ec6@amd.com \
--to=michal.orzel@amd.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=ayan.kumar.halder@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.