From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Alexandru Elisei <alexandru.elisei@arm.com>,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v2 0/2] KVM: arm64: Documentation updates
Date: Wed, 30 Sep 2020 08:31:17 +0100 [thread overview]
Message-ID: <160145106760.805503.16221753406075770666.b4-ty@kernel.org> (raw)
In-Reply-To: <20200924123731.268177-1-alexandru.elisei@arm.com>
On Thu, 24 Sep 2020 13:37:29 +0100, Alexandru Elisei wrote:
> I noticed some discrepancies between the error codes returned by KVM PMU
> emulation and the documentation, this is my attempt at fixing them.
>
> The code is from the original implementation of KVM PMU, and I thought it
> would be more prudent to modify the documentation to match the code instead
> of the other way around.
>
> [...]
Applied to next, thanks!
[1/2] KVM: arm64: Add undocumented return values for PMU device control group
commit: af130d0adc8e48c73030c0d71a59ce1f7809a8fa
[2/2] KVM: arm64: Match PMU error code descriptions with error conditions
commit: 51dd2eb98c72c1ff4cdb1526fff9a259a563c257
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
prev parent reply other threads:[~2020-09-30 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 12:37 [PATCH v2 0/2] KVM: arm64: Documentation updates Alexandru Elisei
2020-09-24 12:37 ` [PATCH v2 1/2] KVM: arm64: Add undocumented return values for PMU device control group Alexandru Elisei
2020-09-24 12:37 ` [PATCH v2 2/2] KVM: arm64: Match PMU error code descriptions with error conditions Alexandru Elisei
2020-09-24 12:59 ` Andrew Jones
2020-09-30 7:31 ` 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=160145106760.805503.16221753406075770666.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).