From: Yeoreum Yun <yeoreum.yun@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: catalin.marinas@arm.com, will@kernel.org,
anshuman.khandual@arm.com, joey.gouly@arm.com,
yury.khrustalev@arm.com, maz@kernel.org, oliver.upton@linux.dev,
frederic@kernel.org, shameerali.kolothum.thodi@huawei.com,
james.morse@arm.com, mark.rutland@arm.com,
huangxiaojia2@huawei.com, akpm@linux-foundation.org,
surenb@google.com, robin.murphy@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 3/3] Documentation/arm64: reflects FEAT_MTE_TAGGED_FAR description
Date: Thu, 3 Apr 2025 18:20:02 +0100 [thread overview]
Message-ID: <Z+7DQnBMc4v6rpm1@e129823.arm.com> (raw)
In-Reply-To: <93497fc3-3da9-43f1-8b22-cf0d3f3e7de2@sirena.org.uk>
Hi Mark,
> On Thu, Apr 03, 2025 at 03:15:35PM +0100, Yeoreum Yun wrote:
> > When FEAT_MTE_TAGGED_FAR feature is supported, the value of address bits
> > [63:60] is preserved on synchronous tag check fault.
> >
> > This patch reflects the above feature in the documentation.
> >
> > Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
> > ---
> > Documentation/arch/arm64/tagged-pointers.rst | 11 ++++++-----
> > 1 file changed, 6 insertions(+), 5 deletions(-)
>
> I saw the subject line and was looking for the elf_hwcaps.rst update in
> this patch, though really it should be in patch 1.
Thanks to let me know. I'll squash it to patch 1.
--
Sincerely,
Yeoreum Yun
prev parent reply other threads:[~2025-04-03 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 14:15 [PATCH 0/3] support FEAT_MTE_TAGGED_FAR feature Yeoreum Yun
2025-04-03 14:15 ` [PATCH 1/3] arm64: add " Yeoreum Yun
2025-04-03 15:13 ` Mark Brown
2025-04-03 17:20 ` Yeoreum Yun
2025-04-03 14:15 ` [PATCH 2/3] arm64/mm/fault: use original FAR_EL1 value when ARM64_MTE_FAR is supported Yeoreum Yun
2025-04-03 14:15 ` [PATCH 3/3] Documentation/arm64: reflects FEAT_MTE_TAGGED_FAR description Yeoreum Yun
2025-04-03 15:31 ` Mark Brown
2025-04-03 17:20 ` Yeoreum Yun [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=Z+7DQnBMc4v6rpm1@e129823.arm.com \
--to=yeoreum.yun@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=frederic@kernel.org \
--cc=huangxiaojia2@huawei.com \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=surenb@google.com \
--cc=will@kernel.org \
--cc=yury.khrustalev@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).