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>,
Luca Fancellu <luca.fancellu@arm.com>,
Hari Limaye <hari.limaye@arm.com>
Subject: Re: [PATCH v4 2/3] arm/mpu: Define arm32 system registers
Date: Tue, 17 Jun 2025 13:27:44 +0200 [thread overview]
Message-ID: <dcb331fa-f4e6-4bff-bad0-c3a0e4c771d9@amd.com> (raw)
In-Reply-To: <20250617111251.1711553-3-ayan.kumar.halder@amd.com>
On 17/06/2025 13:12, Ayan Kumar Halder wrote:
> Fix the definition for HPRLAR.
> Define the base/limit address registers to access the first 32 protection
> regions.
>
> Signed-off-by: Ayan Kumar Halder <ayan.kumar.halder@amd.com>
> Reviewed-by: Hari Limaye <hari.limaye@arm.com>
Acked-by: Michal Orzel <michal.orzel@amd.com>
~Michal
next prev parent reply other threads:[~2025-06-17 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 11:12 [PATCH v4 0/3] Enable R52 support for the first chunk of MPU support Ayan Kumar Halder
2025-06-17 11:12 ` [PATCH v4 1/3] arm/mpu: Move the functions to arm64 specific files Ayan Kumar Halder
2025-06-17 11:27 ` Orzel, Michal
2025-06-17 11:12 ` [PATCH v4 2/3] arm/mpu: Define arm32 system registers Ayan Kumar Halder
2025-06-17 11:27 ` Orzel, Michal [this message]
2025-06-17 11:12 ` [PATCH v4 3/3] arm/mpu: Enable read/write to protection regions for arm32 Ayan Kumar Halder
2025-06-17 12:10 ` Luca Fancellu
2025-06-17 15:31 ` Hari Limaye
2025-06-17 16:28 ` Ayan Kumar Halder
2025-06-19 10:53 ` Julien Grall
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=dcb331fa-f4e6-4bff-bad0-c3a0e4c771d9@amd.com \
--to=michal.orzel@amd.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=ayan.kumar.halder@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=hari.limaye@arm.com \
--cc=julien@xen.org \
--cc=luca.fancellu@arm.com \
--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.