From nobody Tue Apr 28 23:19:29 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 142FBC433F5 for ; Fri, 27 May 2022 10:03:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1350404AbiE0KC6 (ORCPT ); Fri, 27 May 2022 06:02:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45556 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234700AbiE0KCz (ORCPT ); Fri, 27 May 2022 06:02:55 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 168495AA70; Fri, 27 May 2022 03:02:53 -0700 (PDT) Date: Fri, 27 May 2022 10:02:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1653645766; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VaFNPh8tLYLMNVuAM0snkEsxe+g4ELlcZjdA/OStzaQ=; b=1UbL3hjrmBLFZzHC0umqxF98CEBk3HVgpn6eNVZgICVBjh4VGQ5nZUrVD5pZV0c+512xbd smJhbRh3jDGLBdpwHpPaJtGjaM5u6h8iTGqzzgNTJX66q2lTsE8wmyNFH7Ur7hpbMF48Bl 8T4slI5C3MzFzng1Y6VdAJF1wg6HtGIif4LsTz8MsCieceuR15iH0CzE8wdcj5PFAaBvtf +NjnEGaH4eYs0N2/nYsObWwQ7y1i26nlIoKB+A5TyfMBiH/6T4Ss93H19l3pzseGmZAKvt OR+2+bw4NIWdlw2WcM9d3vGVu33qodJqZK8ZbcX9A3c4bqxbnKLr+PWGHhNc1Q== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1653645766; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VaFNPh8tLYLMNVuAM0snkEsxe+g4ELlcZjdA/OStzaQ=; b=T3ZnN2Ql0V4q6Fc5tloVY8DE5T8ixwNiV0b3bxUmIocs6Ozs237iMALT0HqUlvTKOfONt5 tYrBFOOHZPyYSfCA== From: "tip-bot2 for Bo Liu" Sender: tip-bot2@linutronix.de Reply-to: linux-kernel@vger.kernel.org To: linux-tip-commits@vger.kernel.org Subject: [tip: x86/cleanups] x86: Fix all occurences of the "the the" typo Cc: Bo Liu , Ingo Molnar , x86@kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20220527061400.5694-1-liubo03@inspur.com> References: <20220527061400.5694-1-liubo03@inspur.com> MIME-Version: 1.0 Message-ID: <165364576476.4207.9927786337313976000.tip-bot2@tip-bot2> Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The following commit has been merged into the x86/cleanups branch of tip: Commit-ID: b0a2b71fcb99cf2c357692687891b2ce3c0faec2 Gitweb: https://git.kernel.org/tip/b0a2b71fcb99cf2c357692687891b2ce3= c0faec2 Author: Bo Liu AuthorDate: Fri, 27 May 2022 02:14:00 -04:00 Committer: Ingo Molnar CommitterDate: Fri, 27 May 2022 11:58:19 +02:00 x86: Fix all occurences of the "the the" typo Rather than waiting for the bots to fix these one-by-one, fix all occurences of "the the" throughout arch/x86. Signed-off-by: Bo Liu Signed-off-by: Ingo Molnar Link: https://lore.kernel.org/r/20220527061400.5694-1-liubo03@inspur.com --- arch/x86/kvm/vmx/vmx.c | 2 +- arch/x86/kvm/x86.c | 2 +- arch/x86/platform/efi/efi_thunk_64.S | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c index 610355b..2a67350 100644 --- a/arch/x86/kvm/vmx/vmx.c +++ b/arch/x86/kvm/vmx/vmx.c @@ -6221,7 +6221,7 @@ static noinstr void vmx_l1d_flush(struct kvm_vcpu *vc= pu) int size =3D PAGE_SIZE << L1D_CACHE_ORDER; =20 /* - * This code is only executed when the the flush mode is 'cond' or + * This code is only executed when the flush mode is 'cond' or * 'always' */ if (static_branch_likely(&vmx_l1d_flush_cond)) { diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 4790f0d..5f11d7b 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -11855,7 +11855,7 @@ void kvm_arch_destroy_vm(struct kvm *kvm) if (current->mm =3D=3D kvm->mm) { /* * Free memory regions allocated on behalf of userspace, - * unless the the memory map has changed due to process exit + * unless the memory map has changed due to process exit * or fd copying. */ mutex_lock(&kvm->slots_lock); diff --git a/arch/x86/platform/efi/efi_thunk_64.S b/arch/x86/platform/efi/e= fi_thunk_64.S index 854dd81..9ffe2ba 100644 --- a/arch/x86/platform/efi/efi_thunk_64.S +++ b/arch/x86/platform/efi/efi_thunk_64.S @@ -8,7 +8,7 @@ * The below thunking functions are only used after ExitBootServices() * has been called. This simplifies things considerably as compared with * the early EFI thunking because we can leave all the kernel state - * intact (GDT, IDT, etc) and simply invoke the the 32-bit EFI runtime + * intact (GDT, IDT, etc) and simply invoke the 32-bit EFI runtime * services from __KERNEL32_CS. This means we can continue to service * interrupts across an EFI mixed mode call. *