Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp906346ybh; Wed, 22 Jul 2020 16:53:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyZLv09vLn1y72zlP45HJ/eUEMN5VNBS2x3KhWPJZ4RZP33ZvP2tM1b/l4JTg8Qw6DOHzRz X-Received: by 2002:aa7:c655:: with SMTP id z21mr1778950edr.330.1595461998471; Wed, 22 Jul 2020 16:53:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595461998; cv=none; d=google.com; s=arc-20160816; b=EsogvjYtnFo5vT3J7UWxSe/M+D8vz2S6whC4Skm/bSEXM/uR/sHMwNM+aoYHsXvQsa K/ypDFyIj+buvj11lIWcmUf494o+85LV1wyvBaXJn8zVK8XgB2RBTGdOUpebcJBNozjb 5X2gp0F8C2ZrKSLG5lgAK79mseLkgMicwcTpT2FTu40oKceegZ0NU0KQMlOWrzbteNvV EE48W2qDBPax7kMyLO6qSN8RdqqEK6Hz3ImkeNVwFH9Jy7m3HE8/11y4VjQC4Zd730gG 0RMmpII5A3b/ew2H8PQ06E8NtFegkL5E2+TjEWfLq+8rDMCGbqE7janzBpwYCceL60YO Eo/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:date:subject:from:message-id:cc:to; bh=vd1mixG/uVcyIhhP+rEAnaHU/wtNp5nZKofyel7SaF4=; b=m39onHSCu09YJBNbUR0jgwrSdiSWQfJMMno8re/by54w1vcc+HBfn86ZRUpJLKdqq/ dtxGNrqgF++7EF6t3l3llsXPARZfcRDbwN9U4aTxbiRhJe5lJUhiUIVD+L990mFQlI8o B9IcQ++Tb6z/y/dm80Egh/nnv2dzre8N/fT3g/KTYWYQnsZZp5cDN8IG0qOIMWr9RQ/9 fJFluse1RaZQizLDe4DItJCoh909bRcnUOV4XQGH5/z4aZS3F+e2mX5wou2cRYkDCucB sbsfZhMXLmtzLzvkwMKL6Xg6U91eHweLrbykBNY0ZIH4rLbyOonVRuko8oMZ4gNIsgmy Je2w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j7si1131633ejo.679.2020.07.22.16.52.56; Wed, 22 Jul 2020 16:53:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733219AbgGVXuR (ORCPT + 99 others); Wed, 22 Jul 2020 19:50:17 -0400 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:45130 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728607AbgGVXuR (ORCPT ); Wed, 22 Jul 2020 19:50:17 -0400 Received: by kvm5.telegraphics.com.au (Postfix, from userid 502) id 613BF2A2A8; Wed, 22 Jul 2020 19:50:16 -0400 (EDT) To: Geert Uytterhoeven Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org Message-Id: From: Finn Thain Subject: [PATCH] m68k: Correct some typos in comments Date: Thu, 23 Jul 2020 09:25:51 +1000 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Signed-off-by: Finn Thain --- arch/m68k/kernel/head.S | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/arch/m68k/kernel/head.S b/arch/m68k/kernel/head.S index a54788458ca36..08eff92875144 100644 --- a/arch/m68k/kernel/head.S +++ b/arch/m68k/kernel/head.S @@ -57,7 +57,7 @@ * Of course, readability is a subjective issue, so it will never be * argued that that goal was accomplished. It was merely a goal. * A key way to help make code more readable is to give good - * documentation. So, the first thing you will find is exaustive + * documentation. So, the first thing you will find is exhaustive * write-ups on the structure of the file, and the features of the * functional subroutines. * @@ -1304,7 +1304,7 @@ L(mmu_fixup_done): * mmu_engage * * This chunk of code performs the gruesome task of engaging the MMU. - * The reason its gruesome is because when the MMU becomes engaged it + * The reason it's gruesome is because when the MMU becomes engaged it * maps logical addresses to physical addresses. The Program Counter * register is then passed through the MMU before the next instruction * is fetched (the instruction following the engage MMU instruction). @@ -1369,7 +1369,7 @@ L(mmu_fixup_done): /* * After this point no new memory is allocated and * the start of available memory is stored in availmem. - * (The bootmem allocator requires now the physicall address.) + * (The bootmem allocator requires now the physical address.) */ movel L(memory_start),availmem @@ -1547,7 +1547,7 @@ func_return get_bi_record * seven bits of the logical address (LA) are used as an * index into the "root table." Each entry in the root * table has a bit which specifies if it's a valid pointer to a - * pointer table. Each entry defines a 32KMeg range of memory. + * pointer table. Each entry defines a 32Meg range of memory. * If an entry is invalid then that logical range of 32M is * invalid and references to that range of memory (when the MMU * is enabled) will fault. If the entry is valid, then it does @@ -1584,7 +1584,7 @@ func_return get_bi_record * bits 17..12 - index into the Page Table * bits 11..0 - offset into a particular 4K page * - * The algorithms which follows do one thing: they abstract + * The algorithms which follow do one thing: they abstract * the MMU hardware. For example, there are three kinds of * cache settings that are relevant. Either, memory is * being mapped in which case it is either Kernel Code (or @@ -2082,7 +2082,7 @@ func_return mmu_map_tt * mmu_map * * This routine will map a range of memory using a pointer - * table and allocating the pages on the fly from the kernel. + * table and allocate the pages on the fly from the kernel. * The pointer table does not have to be already linked into * the root table, this routine will do that if necessary. * @@ -2528,7 +2528,7 @@ func_start mmu_get_root_table_entry,%d0/%a1 /* Find the start of free memory, get_bi_record does this for us, * as the bootinfo structure is located directly behind the kernel - * and and we simply search for the last entry. + * we simply search for the last entry. */ get_bi_record BI_LAST addw #PAGESIZE-1,%a0 @@ -2654,7 +2654,7 @@ func_start mmu_get_page_table_entry,%d0/%a1 jne 2f /* If the page table entry doesn't exist, we allocate a complete new - * page and use it as one continues big page table which can cover + * page and use it as one continuous big page table which can cover * 4MB of memory, nearly almost all mappings have that alignment. */ get_new_page -- 2.26.2