highmem_32.c : clean up comment
PATCH 1/1 highmem_32.c : clean up comment
clean up comment.
Signed-off-by Figo.zhang <[email protected]>
---arch/x86/mm/highmem_32.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
arch/x86/mm/highmem_32.c +1 -1
@@ -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 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)
PATCH v2 1/1 highmem_32.c : clean up comment
clean up comment.
Signed-off-by Figo.zhang <[email protected]>
---arch/x86/mm/highmem_32.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
arch/x86/mm/highmem_32.c +1 -1
@@ -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)
[tip:x86/mm] x86, highmem_32.c: Clean up comment
Commit-ID: 565b0c1f100408ccbcb04ba458a14da454cb271d Gitweb: http://git.kernel.org/tip/565b0c1f100408ccbcb04ba458a14da454cb271d Author: Figo.zhang <[email protected]> AuthorDate: Mon, 29 Jun 2009 12:02:55 +0800 Committer: Ingo Molnar <[email protected]> CommitDate: Mon, 29 Jun 2009 06:14:43 +0200
x86, highmem_32.c: Clean up comment
Signed-off-by Figo.zhang <[email protected]>
Cc Andrew Morton <[email protected]>
LKML-Reference: <1246248175.5759.12.camel@myhost>
Signed-off-by Ingo Molnar <[email protected]>
--- arch/x86/mm/highmem_32.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
arch/x86/mm/highmem_32.c +1 -1
@@ -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)