From: Andrew Jones <drjones@redhat.com>
To: Steven Price <steven.price@arm.com>
Cc: kvm@vger.kernel.org, linux-doc@vger.kernel.org,
Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Will Deacon <will@kernel.org>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 06/10] KVM: Allow kvm_device_ops to be const
Date: Thu, 3 Oct 2019 15:23:21 +0200 [thread overview]
Message-ID: <20191003132321.jd7wtkbcdmyx7gnv@kamzik.brq.redhat.com> (raw)
In-Reply-To: <20191002145037.51630-7-steven.price@arm.com>
On Wed, Oct 02, 2019 at 03:50:33PM +0100, Steven Price wrote:
> Currently a kvm_device_ops structure cannot be const without triggering
> compiler warnings. However the structure doesn't need to be written to
> and, by marking it const, it can be read-only in memory. Add some more
> const keywords to allow this.
>
> Signed-off-by: Steven Price <steven.price@arm.com>
> ---
> include/linux/kvm_host.h | 4 ++--
> virt/kvm/kvm_main.c | 6 +++---
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
Reviewed-by: Andrew Jones <drjones@redhat.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-03 13:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 14:50 [PATCH v5 00/10] arm64: Stolen time support Steven Price
2019-10-02 14:50 ` [PATCH v5 01/10] KVM: arm64: Document PV-time interface Steven Price
2019-10-03 12:19 ` Andrew Jones
2019-10-04 9:00 ` Steven Price
2019-10-02 14:50 ` [PATCH v5 02/10] KVM: arm/arm64: Factor out hypercall handling from PSCI code Steven Price
2019-10-03 12:23 ` Andrew Jones
2019-10-02 14:50 ` [PATCH v5 03/10] KVM: arm64: Implement PV_FEATURES call Steven Price
2019-10-02 14:50 ` [PATCH v5 04/10] KVM: Implement kvm_put_guest() Steven Price
2019-10-02 14:50 ` [PATCH v5 05/10] KVM: arm64: Support stolen time reporting via shared structure Steven Price
2019-10-03 13:22 ` Andrew Jones
2019-10-04 7:03 ` Andrew Jones
2019-10-04 9:13 ` Steven Price
2019-10-04 9:51 ` Andrew Jones
2019-10-02 14:50 ` [PATCH v5 06/10] KVM: Allow kvm_device_ops to be const Steven Price
2019-10-03 13:23 ` Andrew Jones [this message]
2019-10-02 14:50 ` [PATCH v5 07/10] KVM: arm64: Provide VCPU attributes for stolen time Steven Price
2019-10-02 14:50 ` [PATCH v5 08/10] arm/arm64: Provide a wrapper for SMCCC 1.1 calls Steven Price
2019-10-02 14:50 ` [PATCH v5 09/10] arm/arm64: Make use of the SMCCC 1.1 wrapper Steven Price
2019-10-02 14:50 ` [PATCH v5 10/10] arm64: Retrieve stolen time as paravirtualized guest Steven Price
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=20191003132321.jd7wtkbcdmyx7gnv@kamzik.brq.redhat.com \
--to=drjones@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=steven.price@arm.com \
--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).