mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhang Jiaming <jiaming@nfschina.com>
To: chenhuacai@kernel.org, aleksandar.qemu.devel@gmail.com,
	tsbogend@alpha.franken.de
Cc: linux-mips@vger.kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, liqiong@nfschina.com,
	renyu@nfschina.com, Zhang Jiaming <jiaming@nfschina.com>
Subject: [PATCH] KVM: MIPS/MMU: Fix spelling mistake in a variable
Date: Thu, 30 Jun 2022 21:08:39 +0800	[thread overview]
Message-ID: <20220630130839.9464-1-jiaming@nfschina.com> (raw)

There is a spelling mistake in a variable.
Change 'writeable' to 'writable'.

Signed-off-by: Zhang Jiaming <jiaming@nfschina.com>
---
 arch/mips/kvm/mmu.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/mips/kvm/mmu.c b/arch/mips/kvm/mmu.c
index 1bfd1b501d82..a331407b6b04 100644
--- a/arch/mips/kvm/mmu.c
+++ b/arch/mips/kvm/mmu.c
@@ -594,7 +594,7 @@ static int kvm_mips_map_page(struct kvm_vcpu *vcpu, unsigned long gpa,
 	int srcu_idx, err;
 	kvm_pfn_t pfn;
 	pte_t *ptep, entry, old_pte;
-	bool writeable;
+	bool writable;
 	unsigned long prot_bits;
 	unsigned long mmu_seq;
 
@@ -630,7 +630,7 @@ static int kvm_mips_map_page(struct kvm_vcpu *vcpu, unsigned long gpa,
 	smp_rmb();
 
 	/* Slow path - ask KVM core whether we can access this GPA */
-	pfn = gfn_to_pfn_prot(kvm, gfn, write_fault, &writeable);
+	pfn = gfn_to_pfn_prot(kvm, gfn, write_fault, &writable);
 	if (is_error_noslot_pfn(pfn)) {
 		err = -EFAULT;
 		goto out;
@@ -654,7 +654,7 @@ static int kvm_mips_map_page(struct kvm_vcpu *vcpu, unsigned long gpa,
 
 	/* Set up the PTE */
 	prot_bits = _PAGE_PRESENT | __READABLE | _page_cachable_default;
-	if (writeable) {
+	if (writable) {
 		prot_bits |= _PAGE_WRITE;
 		if (write_fault) {
 			prot_bits |= __WRITEABLE;
-- 
2.25.1


                 reply	other threads:[~2022-06-30 13:08 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=20220630130839.9464-1-jiaming@nfschina.com \
    --to=jiaming@nfschina.com \
    --cc=aleksandar.qemu.devel@gmail.com \
    --cc=chenhuacai@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=liqiong@nfschina.com \
    --cc=renyu@nfschina.com \
    --cc=tsbogend@alpha.franken.de \
    /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

all inboxes | Powered by JetHome®