From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 616C64D124 for ; Wed, 20 Dec 2023 22:49:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="euvCMtNg" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2D486C433C8; Wed, 20 Dec 2023 22:49:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1703112570; bh=LPoPxg5Emt0AXg3ibM2kxTDp2wEp8uU3hpPuk8PCCgg=; h=Date:To:From:Subject:From; b=euvCMtNgg+oeIgx/8a4d5J9k6DEnORpAfGKNwM85xFtDTgbSZMdneW2Kq4D+eduJS VjfQ+QCZERAhHOx+08EJWObOnsmHtKtYPkpxoUln0i2OL0CgqF01DsNFX4fwrnXnsB t5GSiwpDgJ5IiwqZFu5lSWVWWYru8ydEfKluGYCU= Date: Wed, 20 Dec 2023 14:49:29 -0800 To: mm-commits@vger.kernel.org,rdunlap@infradead.org,akpm@linux-foundation.org From: Andrew Morton Subject: [merged mm-stable] gfp-gfp_typesh-fix-typos-punctuation.patch removed from -mm tree Message-Id: <20231220224930.2D486C433C8@smtp.kernel.org> Precedence: bulk X-Mailing-List: mm-commits@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: The quilt patch titled Subject: gfp: gfp_types.h: fix typos & punctuation has been removed from the -mm tree. Its filename was gfp-gfp_typesh-fix-typos-punctuation.patch This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm ------------------------------------------------------ From: Randy Dunlap Subject: gfp: gfp_types.h: fix typos & punctuation Date: Tue, 12 Dec 2023 20:33:16 -0800 Correct typos/spellos and punctutation. Link: https://lkml.kernel.org/r/20231213043316.10128-1-rdunlap@infradead.org Signed-off-by: Randy Dunlap Signed-off-by: Andrew Morton --- include/linux/gfp_types.h | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) --- a/include/linux/gfp_types.h~gfp-gfp_typesh-fix-typos-punctuation +++ a/include/linux/gfp_types.h @@ -162,25 +162,25 @@ typedef unsigned int __bitwise gfp_t; * %__GFP_RECLAIM is shorthand to allow/forbid both direct and kswapd reclaim. * * The default allocator behavior depends on the request size. We have a concept - * of so called costly allocations (with order > %PAGE_ALLOC_COSTLY_ORDER). + * of so-called costly allocations (with order > %PAGE_ALLOC_COSTLY_ORDER). * !costly allocations are too essential to fail so they are implicitly * non-failing by default (with some exceptions like OOM victims might fail so * the caller still has to check for failures) while costly requests try to be * not disruptive and back off even without invoking the OOM killer. * The following three modifiers might be used to override some of these - * implicit rules + * implicit rules. * * %__GFP_NORETRY: The VM implementation will try only very lightweight * memory direct reclaim to get some memory under memory pressure (thus * it can sleep). It will avoid disruptive actions like OOM killer. The * caller must handle the failure which is quite likely to happen under * heavy memory pressure. The flag is suitable when failure can easily be - * handled at small cost, such as reduced throughput + * handled at small cost, such as reduced throughput. * * %__GFP_RETRY_MAYFAIL: The VM implementation will retry memory reclaim * procedures that have previously failed if there is some indication - * that progress has been made else where. It can wait for other - * tasks to attempt high level approaches to freeing memory such as + * that progress has been made elsewhere. It can wait for other + * tasks to attempt high-level approaches to freeing memory such as * compaction (which removes fragmentation) and page-out. * There is still a definite limit to the number of retries, but it is * a larger limit than with %__GFP_NORETRY. @@ -230,7 +230,7 @@ typedef unsigned int __bitwise gfp_t; * is being zeroed (either via __GFP_ZERO or via init_on_alloc, provided that * __GFP_SKIP_ZERO is not set). This flag is intended for optimization: setting * memory tags at the same time as zeroing memory has minimal additional - * performace impact. + * performance impact. * * %__GFP_SKIP_KASAN makes KASAN skip unpoisoning on page allocation. * Used for userspace and vmalloc pages; the latter are unpoisoned by _ Patches currently in -mm which might be from rdunlap@infradead.org are rapidio-tsi721-fix-kernel-doc-warnings.patch freevxfs-bmap-fix-kernel-doc-warnings.patch freevxfs-immed-fix-kernel-doc-param-name.patch freevxfs-lookup-fix-function-params-kernel-doc.patch init-kconfig-move-more-items-into-the-expert-menu.patch usr-kconfig-fix-typos-of-its.patch stacktrace-fix-kernel-doc-typo.patch nilfs2-cpfile-fix-some-kernel-doc-warnings.patch