From: "tip-bot for Figo.zhang" <figo1802@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
figo1802@gmail.com, akpm@osdl.org, tglx@linutronix.de,
mingo@elte.hu
Subject: [tip:x86/mm] x86, highmem_32.c: Clean up comment
Date: Mon, 29 Jun 2009 04:19:23 GMT [thread overview]
Message-ID: <tip-565b0c1f100408ccbcb04ba458a14da454cb271d@git.kernel.org> (raw)
In-Reply-To: <1246248175.5759.12.camel@myhost>
Commit-ID: 565b0c1f100408ccbcb04ba458a14da454cb271d
Gitweb: http://git.kernel.org/tip/565b0c1f100408ccbcb04ba458a14da454cb271d
Author: Figo.zhang <figo1802@gmail.com>
AuthorDate: Mon, 29 Jun 2009 12:02:55 +0800
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Mon, 29 Jun 2009 06:14:43 +0200
x86, highmem_32.c: Clean up comment
Signed-off-by: Figo.zhang <figo1802@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>
LKML-Reference: <1246248175.5759.12.camel@myhost>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/mm/highmem_32.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/mm/highmem_32.c b/arch/x86/mm/highmem_32.c
index 58f621e..0c6f43c 100644
--- a/arch/x86/mm/highmem_32.c
+++ b/arch/x86/mm/highmem_32.c
@@ -24,7 +24,7 @@ void kunmap(struct page *page)
* no global lock is needed and because the kmap code must perform a global TLB
* invalidation when the kmap pool wraps.
*
- * However when holding an atomic kmap is is not legal to sleep, so atomic
+ * However when holding an atomic kmap it is not legal to sleep, so atomic
* kmaps are appropriate for short, tight code paths only.
*/
void *kmap_atomic_prot(struct page *page, enum km_type type, pgprot_t prot)
prev parent reply other threads:[~2009-06-29 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 2:22 [PATCH]highmem_32.c : clean up comment Figo.zhang
2009-06-29 4:02 ` [PATCH v2]highmem_32.c " Figo.zhang
2009-06-29 4:19 ` tip-bot for Figo.zhang [this message]
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=tip-565b0c1f100408ccbcb04ba458a14da454cb271d@git.kernel.org \
--to=figo1802@gmail.com \
--cc=akpm@osdl.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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