linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michael DeGuzis <mdeguzis@gmail.com>
To: linux-mm@kvack.org
Cc: trivial@kernel.org, Michael DeGuzis <mdeguzis@gmail.com>
Subject: [PATCH v2] PATCH [PATCH 001] memory management: spelling and grammar
Date: Wed, 17 May 2017 15:19:21 -0400	[thread overview]
Message-ID: <20170517191921.14415-1-mdeguzis@gmail.com> (raw)

This patch fixes up some grammar and spelling in the
information block for huge_memory.c.

* Fix grammary/spelling in mm/huge_memory.c

Signed-off-by: Michael DeGuzis <mdeguzis@gmail.com>
---
 mm/huge_memory.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index a84909cf20d3..b75b8f08eb86 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -38,10 +38,10 @@
 #include "internal.h"
 
 /*
- * By default transparent hugepage support is disabled in order that avoid
- * to risk increase the memory footprint of applications without a guaranteed
- * benefit. When transparent hugepage support is enabled, is for all mappings,
- * and khugepaged scans all mappings.
+ * By default, transparent hugepage support is disabled in order to avoid
+ * risking an increased memory footprint for applications that are not
+ * guaranteed to benefit from it. When transparent hugepage support is
+ * enabled, it is for all mappings, and khugepaged scans all mappings.
  * Defrag is invoked by khugepaged hugepage allocations and by page faults
  * for all hugepage allocations.
  */
-- 
2.12.2

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

                 reply	other threads:[~2017-05-17 19:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170517191921.14415-1-mdeguzis@gmail.com \
    --to=mdeguzis@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=trivial@kernel.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).