From: Mao Wenan <maowenan@huawei.com> To: <pbonzini@redhat.com>, <rkrcmar@redhat.com>, <sean.j.christopherson@intel.com>, <vkuznets@redhat.com>, <wanpengli@tencent.com>, <jmattson@google.com>, <joro@8bytes.org>, <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>, <hpa@zytor.com> Cc: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>, Mao Wenan <maowenan@huawei.com> Subject: [PATCH -next] KVM: x86: remove set but not used variable 'called' Date: Tue, 19 Nov 2019 11:06:40 +0800 [thread overview] Message-ID: <20191119030640.25097-1-maowenan@huawei.com> (raw) Fixes gcc '-Wunused-but-set-variable' warning: arch/x86/kvm/x86.c: In function kvm_make_scan_ioapic_request_mask: arch/x86/kvm/x86.c:7911:7: warning: variable called set but not used [-Wunused-but-set-variable] It is not used since commit 7ee30bc132c6 ("KVM: x86: deliver KVM IOAPIC scan request to target vCPUs") Signed-off-by: Mao Wenan <maowenan@huawei.com> --- arch/x86/kvm/x86.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 0d0a682..870f0bc 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -7908,12 +7908,11 @@ void kvm_make_scan_ioapic_request_mask(struct kvm *kvm, unsigned long *vcpu_bitmap) { cpumask_var_t cpus; - bool called; zalloc_cpumask_var(&cpus, GFP_ATOMIC); - called = kvm_make_vcpus_request_mask(kvm, KVM_REQ_SCAN_IOAPIC, - vcpu_bitmap, cpus); + kvm_make_vcpus_request_mask(kvm, KVM_REQ_SCAN_IOAPIC, + vcpu_bitmap, cpus); free_cpumask_var(cpus); } -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Mao Wenan <maowenan@huawei.com> To: pbonzini@redhat.com, rkrcmar@redhat.com, sean.j.christopherson@intel.com, vkuznets@redhat.com, wanpengli@tencent.com, jmattson@google.com, joro@8bytes.org, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, hpa@zytor.com Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org, Mao Wenan <maowenan@huawei.com> Subject: [PATCH -next] KVM: x86: remove set but not used variable 'called' Date: Tue, 19 Nov 2019 03:06:40 +0000 [thread overview] Message-ID: <20191119030640.25097-1-maowenan@huawei.com> (raw) Fixes gcc '-Wunused-but-set-variable' warning: arch/x86/kvm/x86.c: In function kvm_make_scan_ioapic_request_mask: arch/x86/kvm/x86.c:7911:7: warning: variable called set but not used [-Wunused-but-set-variable] It is not used since commit 7ee30bc132c6 ("KVM: x86: deliver KVM IOAPIC scan request to target vCPUs") Signed-off-by: Mao Wenan <maowenan@huawei.com> --- arch/x86/kvm/x86.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 0d0a682..870f0bc 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -7908,12 +7908,11 @@ void kvm_make_scan_ioapic_request_mask(struct kvm *kvm, unsigned long *vcpu_bitmap) { cpumask_var_t cpus; - bool called; zalloc_cpumask_var(&cpus, GFP_ATOMIC); - called = kvm_make_vcpus_request_mask(kvm, KVM_REQ_SCAN_IOAPIC, - vcpu_bitmap, cpus); + kvm_make_vcpus_request_mask(kvm, KVM_REQ_SCAN_IOAPIC, + vcpu_bitmap, cpus); free_cpumask_var(cpus); } -- 2.7.4
next reply other threads:[~2019-11-19 3:08 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-19 3:06 Mao Wenan [this message] 2019-11-19 3:06 ` [PATCH -next] KVM: x86: remove set but not used variable 'called' Mao Wenan 2019-11-19 11:58 ` Vitaly Kuznetsov 2019-11-19 11:58 ` Vitaly Kuznetsov 2019-11-19 12:14 ` Dan Carpenter 2019-11-19 12:14 ` Dan Carpenter 2019-11-19 12:28 ` Vitaly Kuznetsov 2019-11-19 12:28 ` Vitaly Kuznetsov 2019-11-19 12:39 ` Dan Carpenter 2019-11-19 12:39 ` Dan Carpenter 2019-11-19 13:25 ` Vitaly Kuznetsov 2019-11-19 13:25 ` Vitaly Kuznetsov 2019-11-22 11:58 ` Nitesh Narayan Lal 2019-11-22 11:58 ` Nitesh Narayan Lal 2019-11-22 12:25 ` Dan Carpenter 2019-11-22 12:25 ` Dan Carpenter 2019-11-22 12:45 ` Nitesh Narayan Lal 2019-11-22 12:45 ` Nitesh Narayan Lal 2019-11-21 9:13 ` Paolo Bonzini 2019-11-21 9:13 ` Paolo Bonzini 2019-11-22 0:48 ` maowenan 2019-11-22 0:48 ` maowenan 2019-11-22 2:39 ` [PATCH -next v2] " Mao Wenan 2019-11-22 2:39 ` Mao Wenan 2019-11-19 12:42 ` [PATCH -next] " maowenan 2019-11-19 12:42 ` maowenan 2019-11-19 13:27 ` Vitaly Kuznetsov 2019-11-19 13:27 ` Vitaly Kuznetsov
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=20191119030640.25097-1-maowenan@huawei.com \ --to=maowenan@huawei.com \ --cc=bp@alien8.de \ --cc=hpa@zytor.com \ --cc=jmattson@google.com \ --cc=joro@8bytes.org \ --cc=kernel-janitors@vger.kernel.org \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@redhat.com \ --cc=pbonzini@redhat.com \ --cc=rkrcmar@redhat.com \ --cc=sean.j.christopherson@intel.com \ --cc=tglx@linutronix.de \ --cc=vkuznets@redhat.com \ --cc=wanpengli@tencent.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.