[tip:x86/mm] x86, highmem_32.c: Clean up comment

[tip-bot for Figo.zhang]

Commit-ID:  565b0c1f100408ccbcb04ba458a14da454cb271d
Gitweb:     http://git.kernel.org/tip/565b0c1f100408ccbcb04ba458a14da454cb271d
Author:     Figo.zhang <figo1802@xxxxxxxxx>
AuthorDate: Mon, 29 Jun 2009 12:02:55 +0800
Committer:  Ingo Molnar <mingo@xxxxxxx>
CommitDate: Mon, 29 Jun 2009 06:14:43 +0200

x86, highmem_32.c: Clean up comment

Signed-off-by: Figo.zhang <figo1802@xxxxxxxxx>
Cc: Andrew Morton <akpm@xxxxxxxx>
LKML-Reference: <1246248175.5759.12.camel@myhost>
Signed-off-by: Ingo Molnar <mingo@xxxxxxx>


---
 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)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/