From: Randy Dunlap <rdunlap@infradead.org>
To: linux-mm@kvack.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 04/15] mm: hugetlb.c: delete duplicated words
Date: Sat, 1 Aug 2020 10:38:11 -0700 [thread overview]
Message-ID: <20200801173822.14973-5-rdunlap@infradead.org> (raw)
In-Reply-To: <20200801173822.14973-1-rdunlap@infradead.org>
Drop the repeated word "the" in two places.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
To: linux-mm@kvack.org
---
mm/hugetlb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20200731.orig/mm/hugetlb.c
+++ linux-next-20200731/mm/hugetlb.c
@@ -134,7 +134,7 @@ void hugepage_put_subpool(struct hugepag
/*
* Subpool accounting for allocating and reserving pages.
* Return -ENOMEM if there are not enough resources to satisfy the
- * the request. Otherwise, return the number of pages by which the
+ * request. Otherwise, return the number of pages by which the
* global pools must be adjusted (upward). The returned value may
* only be different than the passed value (delta) in the case where
* a subpool minimum size must be maintained.
@@ -2174,7 +2174,7 @@ static void return_unused_surplus_pages(
* evenly across all nodes with memory. Iterate across these nodes
* until we can no longer free unreserved surplus pages. This occurs
* when the nodes with surplus pages have no free pages.
- * free_pool_huge_page() will balance the the freed pages across the
+ * free_pool_huge_page() will balance the freed pages across the
* on-line nodes with memory and will handle the hstate accounting.
*
* Note that we decrement resv_huge_pages as we free the pages. If
next prev parent reply other threads:[~2020-08-01 18:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 17:38 [PATCH 00/15] mm: delete duplicated words and fix typos Randy Dunlap
2020-08-01 17:38 ` [PATCH 01/15] mm: compaction.c: delete duplicated word Randy Dunlap
2020-08-01 17:38 ` [PATCH 02/15] mm: filemap.c: " Randy Dunlap
2020-08-01 17:38 ` [PATCH 03/15] mm: hmm.c: " Randy Dunlap
2020-08-01 17:38 ` Randy Dunlap [this message]
2020-08-05 19:53 ` [PATCH 04/15] mm: hugetlb.c: delete duplicated words Mike Kravetz
2020-08-01 17:38 ` [PATCH 05/15] mm: memcontrol.c: " Randy Dunlap
2020-08-01 17:38 ` [PATCH 06/15] mm: memory.c: " Randy Dunlap
2020-08-01 17:38 ` [PATCH 07/15] mm: migrate.c: delete duplicated word Randy Dunlap
2020-08-01 17:38 ` [PATCH 08/15] mm: nommu.c: delete duplicated words Randy Dunlap
2020-08-01 17:38 ` [PATCH 09/15] mm: page_alloc.c: delete or fix " Randy Dunlap
2020-08-01 17:38 ` [PATCH 10/15] mm: shmem.c: delete duplicated word Randy Dunlap
2020-08-01 17:38 ` [PATCH 11/15] mm: slab_common.c: " Randy Dunlap
2020-08-01 17:38 ` [PATCH 12/15] mm: usercopy.c: " Randy Dunlap
2020-08-01 17:38 ` [PATCH 13/15] mm: vmscan.c: delete or fix duplicated words Randy Dunlap
2020-08-01 17:38 ` [PATCH 14/15] mm: zpool.c: delete duplicated word and fix grammar Randy Dunlap
2020-08-01 17:38 ` [PATCH 15/15] mm: zsmalloc.c: fix duplicated words Randy Dunlap
2020-08-05 22:20 ` [PATCH 00/15] mm: delete duplicated words and fix typos Zi Yan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200801173822.14973-5-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).