From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jiri Kosina <trivial@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Johannes Weiner <hannes@cmpxchg.org>,
cgroups@vger.kernel.org
Subject: [PATCH -trivial 3/4] mm: memcontrol: Spelling s/invlidate/invalidate/, s/trucate/truncate/
Date: Sun, 29 Jun 2014 12:21:38 +0200 [thread overview]
Message-ID: <1404037299-31570-3-git-send-email-geert@linux-m68k.org> (raw)
In-Reply-To: <1404037299-31570-1-git-send-email-geert@linux-m68k.org>
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: cgroups@vger.kernel.org
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index a2c7bcb0e6eb..2c010573668e 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -4034,7 +4034,7 @@ void mem_cgroup_uncharge_cache_page(struct page *page)
}
/*
- * Batch_start/batch_end is called in unmap_page_range/invlidate/trucate.
+ * Batch_start/batch_end is called in unmap_page_range/invalidate/truncate.
* In that cases, pages are freed continuously and we can expect pages
* are in the same memcg. All these calls itself limits the number of
* pages freed at once, then uncharge_start/end() is called properly.
--
1.9.1
next prev parent reply other threads:[~2014-06-29 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 10:21 [PATCH -trivial 1/4] powerpc/simpleboot: Spelling s/trucate/truncate/ Geert Uytterhoeven
2014-06-29 10:21 ` [PATCH -trivial 2/4] mtd: cmdlinepart: " Geert Uytterhoeven
2014-07-03 0:26 ` Brian Norris
2014-06-29 10:21 ` Geert Uytterhoeven [this message]
2014-06-29 10:21 ` [PATCH -trivial 4/4] GFS2: memcontrol: Spelling s/invlidate/invalidate/ Geert Uytterhoeven
2014-06-30 15:30 ` [Cluster-devel] " Bob Peterson
2014-07-03 14:20 ` Steven Whitehouse
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=1404037299-31570-3-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®