aboutsummaryrefslogtreecommitdiffstats
path: root/arch/cris/mm
diff options
context:
space:
mode:
authorAndré Goddard Rosa <andre.goddard@gmail.com>2009-11-14 10:09:05 -0500
committerJiri Kosina <jkosina@suse.cz>2009-12-04 09:39:55 -0500
commitaf901ca181d92aac3a7dc265144a9081a86d8f39 (patch)
tree380054af22521144fbe1364c3bcd55ad24c9bde4 /arch/cris/mm
parent972b94ffb90ea6d20c589d9a47215df103388ddd (diff)
tree-wide: fix assorted typos all over the place
That is "success", "unknown", "through", "performance", "[re|un]mapping" , "access", "default", "reasonable", "[con]currently", "temperature" , "channel", "[un]used", "application", "example","hierarchy", "therefore" , "[over|under]flow", "contiguous", "threshold", "enough" and others. Signed-off-by: André Goddard Rosa <andre.goddard@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'arch/cris/mm')
-rw-r--r--arch/cris/mm/fault.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/cris/mm/fault.c b/arch/cris/mm/fault.c
index 4a7cdd9ea1ee..380df1a73a6e 100644
--- a/arch/cris/mm/fault.c
+++ b/arch/cris/mm/fault.c
@@ -209,7 +209,7 @@ do_page_fault(unsigned long address, struct pt_regs *regs,
209 /* Are we prepared to handle this kernel fault? 209 /* Are we prepared to handle this kernel fault?
210 * 210 *
211 * (The kernel has valid exception-points in the source 211 * (The kernel has valid exception-points in the source
212 * when it acesses user-memory. When it fails in one 212 * when it accesses user-memory. When it fails in one
213 * of those points, we find it in a table and do a jump 213 * of those points, we find it in a table and do a jump
214 * to some fixup code that loads an appropriate error 214 * to some fixup code that loads an appropriate error
215 * code) 215 * code)