From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 723E3C2D0C9 for ; Sat, 14 Dec 2019 12:29:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 49A7624656 for ; Sat, 14 Dec 2019 12:29:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="TdT7jtcC" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726636AbfLNM3O (ORCPT ); Sat, 14 Dec 2019 07:29:14 -0500 Received: from mail.skyhub.de ([5.9.137.197]:54140 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725872AbfLNM3O (ORCPT ); Sat, 14 Dec 2019 07:29:14 -0500 Received: from zn.tnic (p200300EC2F0A5A009CBB5BB8E6A81C1F.dip0.t-ipconnect.de [IPv6:2003:ec:2f0a:5a00:9cbb:5bb8:e6a8:1c1f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id E3E281EC095C; Sat, 14 Dec 2019 13:29:11 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1576326552; h=from:from: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:in-reply-to:in-reply-to: references:references; bh=8NCoc4fb2yRyFtctOcE7NM5N1P1G1fFp8+EyemH6LM8=; b=TdT7jtcCxSBC/j3j6arokG0EX5msVb8eN5aWP4jJdYexOAWLvsWeWZBIvvXmkU0X9ArVuS YwGvoKUlJJYh8ZU5WSbTyEDdtEZaZSYfT/PXnaXXQCE4JfA3hjcMEIhY8tJDVf8l7s5MbZ NqxojWGpiWAs15TS2oWFCWsHAH08fLE= Date: Sat, 14 Dec 2019 13:29:10 +0100 From: Borislav Petkov To: Bhupesh Sharma Cc: linux-kernel@vger.kernel.org, bhupesh.linux@gmail.com, x86@kernel.org, linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org, kexec@lists.infradead.org, Jonathan Corbet , James Morse , Mark Rutland , Will Deacon , Steve Capper , Catalin Marinas , Ard Biesheuvel Subject: Re: [PATCH v5 3/5] Documentation/arm64: Fix a simple typo in memory.rst Message-ID: <20191214122910.GD28635@zn.tnic> References: <1574972716-25858-1-git-send-email-bhsharma@redhat.com> <1574972716-25858-2-git-send-email-bhsharma@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1574972716-25858-2-git-send-email-bhsharma@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 29, 2019 at 01:55:14AM +0530, Bhupesh Sharma wrote: > Fix a simple typo in arm64/memory.rst > > Cc: Jonathan Corbet > Cc: James Morse > Cc: Mark Rutland > Cc: Will Deacon > Cc: Steve Capper > Cc: Catalin Marinas > Cc: Ard Biesheuvel > Cc: linux-doc@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Cc: linux-arm-kernel@lists.infradead.org > Signed-off-by: Bhupesh Sharma > --- > Documentation/arm64/memory.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/arm64/memory.rst b/Documentation/arm64/memory.rst > index 02e02175e6f5..cf03b3290800 100644 > --- a/Documentation/arm64/memory.rst > +++ b/Documentation/arm64/memory.rst > @@ -129,7 +129,7 @@ this logic. > > As a single binary will need to support both 48-bit and 52-bit VA > spaces, the VMEMMAP must be sized large enough for 52-bit VAs and > -also must be sized large enought to accommodate a fixed PAGE_OFFSET. > +also must be sized large enough to accommodate a fixed PAGE_OFFSET. > > Most code in the kernel should not need to consider the VA_BITS, for > code that does need to know the VA size the variables are > -- Why is this a separate patch? -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette