From: linmiaohe <linmiaohe@huawei.com>
To: Auger Eric <eric.auger@redhat.com>,
"maz@kernel.org" <maz@kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"julien.thierry.kdev@gmail.com" <julien.thierry.kdev@gmail.com>,
"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>,
"christoffer.dall@arm.com" <christoffer.dall@arm.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"will@kernel.org" <will@kernel.org>,
"andre.przywara@arm.com" <andre.przywara@arm.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: vgic: Use warpper function to lock/unlock all vcpus in kvm_vgic_create()
Date: Thu, 28 Nov 2019 09:20:18 +0000 [thread overview]
Message-ID: <ba063b6de6b14fedb09c9d382120bf46@huawei.com> (raw)
Eric wrote:
>> From: Miaohe Lin <linmiaohe@huawei.com>
>>
>> Use warpper function lock_all_vcpus()/unlock_all_vcpus()
> s/warpper/wrapper and also in the title.
Hi, Eric:
Many thanks for your review. I would fix this and send a patch v2.
Thanks again.
next reply other threads:[~2019-11-28 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 9:20 linmiaohe [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-28 3:09 [PATCH] KVM: vgic: Use warpper function to lock/unlock all vcpus in kvm_vgic_create() linmiaohe
2019-11-28 9:07 ` Auger Eric
2019-11-28 9:44 ` Marc Gonzalez
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=ba063b6de6b14fedb09c9d382120bf46@huawei.com \
--to=linmiaohe@huawei.com \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=eric.auger@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.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=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.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).