From: Marc Zyngier <maz@kernel.org>
To: Shuah Khan <shuah@kernel.org>, James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Mark Brown <broonie@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvmarm@lists.cs.columbia.edu, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
kvmarm@lists.linux.dev
Subject: Re: [PATCH] KVM: selftests: Comment newly defined aarch64 ID registers
Date: Thu, 30 Mar 2023 19:36:40 +0100 [thread overview]
Message-ID: <168020137263.2928811.17818643951034936761.b4-ty@kernel.org> (raw)
In-Reply-To: <20230210-kvm-arm64-getreg-comments-v1-1-a16c73be5ab4@kernel.org>
On Mon, 06 Mar 2023 16:15:07 +0000, Mark Brown wrote:
> All otherwise unspecified aarch64 ID registers should be read as zero so
> we cover the whole ID register space in the get-reg-list test but we've
> added comments for those that have been named. Add comments for
> ID_AA64PFR2_EL1, ID_AA64SMFR0_EL1, ID_AA64ISAR2_EL1, ID_AA64MMFR3_EL1
> and ID_AA64MMFR4_EL1 which have been defined since the comments were
> added so someone looking for them will see that they are covered.
Applied to next, thanks!
[1/1] KVM: selftests: Comment newly defined aarch64 ID registers
commit: 767cc0501bbb51f2daad35d1bc4f6eaa857ed057
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2023-03-30 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 16:15 [PATCH] KVM: selftests: Comment newly defined aarch64 ID registers Mark Brown
2023-03-30 18:36 ` Marc Zyngier [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=168020137263.2928811.17818643951034936761.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=broonie@kernel.org \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@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