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=-3.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS autolearn=no 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 C2E04C432C0 for ; Sun, 1 Dec 2019 01:58:19 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 88032205ED for ; Sun, 1 Dec 2019 01:58:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="qW/sie8U" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 88032205ED Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 35D066B039B; Sat, 30 Nov 2019 20:58:19 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 30E756B039D; Sat, 30 Nov 2019 20:58:19 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 227286B039E; Sat, 30 Nov 2019 20:58:19 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0207.hostedemail.com [216.40.44.207]) by kanga.kvack.org (Postfix) with ESMTP id 0A29D6B039B for ; Sat, 30 Nov 2019 20:58:19 -0500 (EST) Received: from smtpin20.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with SMTP id B7396824999B for ; Sun, 1 Dec 2019 01:58:18 +0000 (UTC) X-FDA: 76214912676.20.move85_488b27475ff2f X-HE-Tag: move85_488b27475ff2f X-Filterd-Recvd-Size: 2757 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf19.hostedemail.com (Postfix) with ESMTP for ; Sun, 1 Dec 2019 01:58:18 +0000 (UTC) Received: from localhost.localdomain (c-73-231-172-41.hsd1.ca.comcast.net [73.231.172.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9858B2231B; Sun, 1 Dec 2019 01:58:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1575165497; bh=9E9dAij0q9QfEpJ1LXg2YO3y9ARcfzAtKub0GvgVjFI=; h=Date:From:To:Subject:From; b=qW/sie8U1jNHUffXfWg+uY8ncf8LOJ6ATkJSiVN2Td6GvlcfEFNg1wv6Wp91T6Rut DbN8+9vcFCYeJuqaf9uKNfNl1lbLF7Wp7xw4F5BZDyzXey0Disvp0QSGvOMNjLC0m/ m6ATutL8KHtWi0acxUIjd76I6sub2sQv0tgrg9u8= Date: Sat, 30 Nov 2019 17:58:17 -0800 From: akpm@linux-foundation.org To: akpm@linux-foundation.org, linux-mm@kvack.org, mm-commits@vger.kernel.org, richardw.yang@linux.intel.com, torvalds@linux-foundation.org Subject: [patch 154/158] mm: fix typos in comments when calling __SetPageUptodate() Message-ID: <20191201015817.izJ8MDym6%akpm@linux-foundation.org> User-Agent: s-nail v14.8.16 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: From: Wei Yang Subject: mm: fix typos in comments when calling __SetPageUptodate() There are several places emphasise the effect of __SetPageUptodate(), while the comment seems to have a typo in two places. Link: http://lkml.kernel.org/r/20190926023705.7226-1-richardw.yang@linux.intel.com Signed-off-by: Wei Yang Reviewed-by: Andrew Morton Signed-off-by: Andrew Morton --- mm/memory.c | 2 +- mm/userfaultfd.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) --- a/mm/memory.c~mm-fix-typo-in-the-comment-when-calling-function-__setpageuptodate +++ a/mm/memory.c @@ -3105,7 +3105,7 @@ static vm_fault_t do_anonymous_page(stru /* * The memory barrier inside __SetPageUptodate makes sure that - * preceeding stores to the page contents become visible before + * preceding stores to the page contents become visible before * the set_pte_at() write. */ __SetPageUptodate(page); --- a/mm/userfaultfd.c~mm-fix-typo-in-the-comment-when-calling-function-__setpageuptodate +++ a/mm/userfaultfd.c @@ -90,7 +90,7 @@ static int mcopy_atomic_pte(struct mm_st /* * The memory barrier inside __SetPageUptodate makes sure that - * preceeding stores to the page contents become visible before + * preceding stores to the page contents become visible before * the set_pte_at() write. */ __SetPageUptodate(page); _