From: Marc Zyngier <maz@kernel.org>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
Keqian Zhu <zhukeqian1@huawei.com>,
kvmarm@lists.cs.columbia.edu
Cc: Will Deacon <will@kernel.org>, Andrew Jones <drjones@redhat.com>,
James Morse <james.morse@arm.com>,
Steven Price <steven.price@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
wanghaibin.wang@huawei.com,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH v2 0/2] KVM: arm64: Some fixes and code adjustments for pvtime ST
Date: Thu, 3 Dec 2020 19:03:28 +0000 [thread overview]
Message-ID: <160702219014.403179.5103308104909161941.b4-ty@kernel.org> (raw)
In-Reply-To: <20200817110728.12196-1-zhukeqian1@huawei.com>
On Mon, 17 Aug 2020 19:07:26 +0800, Keqian Zhu wrote:
> During picking up pvtime LPT support for arm64, I do some trivial fixes for
> pvtime ST.
>
> change log:
>
> v2:
> - Add Andrew's and Steven's R-b.
> - Correct commit message of the first patch.
> - Drop the second patch.
>
> [...]
Applied to kvm-arm64/misc-5.11, thanks!
[1/2] KVM: arm64: Some fixes of PV-time interface document
commit: 94558543213ae8c83be5d01b83c1fe7530e8a1a0
[2/2] KVM: arm64: Use kvm_write_guest_lock when init stolen time
commit: 652d0b701d136ede6bc8a977b3abbe2d420226b9
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2020-12-03 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 11:07 Keqian Zhu
2020-08-17 11:07 ` [PATCH v2 1/2] KVM: arm64: Some fixes of PV-time interface document Keqian Zhu
2020-12-03 15:04 ` Marc Zyngier
2020-12-04 6:08 ` zhukeqian
2020-08-17 11:07 ` [PATCH v2 2/2] KVM: arm64: Use kvm_write_guest_lock when init stolen time Keqian Zhu
2020-12-03 14:16 ` [PATCH v2 0/2] KVM: arm64: Some fixes and code adjustments for pvtime ST zhukeqian
2020-12-03 19:03 ` 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=160702219014.403179.5103308104909161941.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=drjones@redhat.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.org \
--cc=zhukeqian1@huawei.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
all inboxes | Powered by JetHome®