kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yan Zhu <zhuyan34@huawei.com>
To: <pbonzini@redhat.com>, <rkrcmar@redhat.com>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
	<x86@kernel.org>, <kvm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <liucheng32@huawei.com>
Subject: [PATCH] KVM: x86: fix mmu_set_spte coding style warning
Date: Wed, 19 Feb 2020 20:50:51 +0800	[thread overview]
Message-ID: <20200219125051.49529-1-zhuyan34@huawei.com> (raw)

checkpatch.pl warns:

ERROR: code indent should use tabs where possible
+^I^I       ^Ibool speculative, bool host_writable)$

WARNING: please, no space before tabs
+^I^I       ^Ibool speculative, bool host_writable)$

This warning occurs because there is a space before the tab on this line.
Remove them so that the indentation is consistent with the Linux kernel
coding style

Fixes: 61524f1bccc0 ("KVM: x86: extend usage of RET_MMIO_PF_* constants")
Signed-off-by: Yan Zhu <zhuyan34@huawei.com>
---
 arch/x86/kvm/mmu.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 3a281a2decde..0d403f41afc5 100644
--- a/arch/x86/kvm/mmu.c
+++ b/arch/x86/kvm/mmu.c
@@ -2682,7 +2682,7 @@ static int set_spte(struct kvm_vcpu *vcpu, u64 *sptep,
 
 static int mmu_set_spte(struct kvm_vcpu *vcpu, u64 *sptep, unsigned pte_access,
 			int write_fault, int level, gfn_t gfn, kvm_pfn_t pfn,
-		       	bool speculative, bool host_writable)
+			bool speculative, bool host_writable)
 {
 	int was_rmapped = 0;
 	int rmap_count;
-- 
2.12.3


                 reply	other threads:[~2020-02-19 12:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200219125051.49529-1-zhuyan34@huawei.com \
    --to=zhuyan34@huawei.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liucheng32@huawei.com \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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).