From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm/arm64: prefer IS_ENABLED to a static variable
Date: Wed, 11 Mar 2015 15:20:24 +0100 [thread overview]
Message-ID: <20150311142024.GA23478@cbox> (raw)
In-Reply-To: <1425554766-4119-1-git-send-email-pbonzini@redhat.com>
On Thu, Mar 05, 2015 at 12:26:06PM +0100, Paolo Bonzini wrote:
> IS_ENABLED gives compile-time checking and keeps the code clearer.
>
> The one exception is inside kvm_vm_ioctl_check_extension, where
> the established idiom is to wrap the case labels with an #ifdef.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Thanks, I've applied this to my queue with a follow-up to remove config
options all together just like we have it on arm64.
I'll send out that patch based on yours and I've applied Eric's IRQFD
series on top of that.
Best,
-Christoffer
prev parent reply other threads:[~2015-03-11 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 11:26 [PATCH] KVM: arm/arm64: prefer IS_ENABLED to a static variable Paolo Bonzini
2015-03-11 14:20 ` Christoffer Dall [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=20150311142024.GA23478@cbox \
--to=christoffer.dall@linaro.org \
--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).