typo fixes: occuring -> occurring
Subsystems (8)
PATCH 1/1 typo fixes: occuring -> occurring
Signed-off-by Adrian Bunk <[email protected]>
---
Documentation/feature-list-2.6.txt | 2 +- Documentation/memory-barriers.txt | 2 +- arch/i386/mm/fault.c | 2 +- arch/m32r/mm/fault.c | 2 +- arch/powerpc/platforms/powermac/cpufreq_32.c | 2 +- arch/powerpc/platforms/pseries/eeh_driver.c | 2 +- arch/x86_64/mm/fault.c | 2 +- drivers/infiniband/hw/ipath/ipath_intr.c | 2 +- drivers/message/fusion/mptbase.c | 2 +- drivers/net/wireless/ipw2100.c | 2 +- drivers/serial/pxa.c | 2 +- include/asm-arm/thread_info.h | 2 +- include/asm-ia64/sn/tioca_provider.h | 2 +- kernel/cpuset.c | 2 +- 14 files changed, 14 insertions(+), 14 deletions(-)
Documentation/memory-barriers.txt renamed from Documentation/memory-barriers.txt.old +1 -1
@@ -602,7 +602,7 @@ This sequence of events is committed to the memory coherence system in an order that the rest of the system might perceive as the unordered set of { STORE A, -STORE B, STORE C } all occuring before the unordered set of { STORE D, STORE E +STORE B, STORE C } all occurring before the unordered set of { STORE D, STORE E }: +-------+ : :
Documentation/feature-list-2.6.txt renamed from Documentation/feature-list-2.6.txt.old +1 -1
@@ -963,7 +963,7 @@ ~~~~~~~~~~~~~~~~~~~~~~~~~~ The machine check handler has been extended so that it regularly polls for any problems on AMD Athlon, and Intel Pentium 4 systems. -This may result in machine check exceptions occuring more frequently +This may result in machine check exceptions occurring more frequently than they did in 2.4 on out of spec systems (Overclocking/inadequate cooling/underated PSU etc..).
arch/i386/mm/fault.c renamed from arch/i386/mm/fault.c.old +1 -1
@@ -389,7 +389,7 @@/* When running in the kernel we expect faults to occur only to * addresses in user space. All other faults represent errors in the * kernel and should generate an OOPS. Unfortunatly, in the case of an -* erroneous fault occuring in a code path which already holds mmap_sem +* erroneous fault occurring in a code path which already holds mmap_sem * we will deadlock attempting to validate the fault against the * address space. Luckily the kernel only validly references user * space from well defined areas of code, which are listed in the
arch/m32r/mm/fault.c renamed from arch/m32r/mm/fault.c.old +1 -1
@@ -148,7 +148,7 @@/* When running in the kernel we expect faults to occur only to * addresses in user space. All other faults represent errors in the * kernel and should generate an OOPS. Unfortunatly, in the case of an -* erroneous fault occuring in a code path which already holds mmap_sem +* erroneous fault occurring in a code path which already holds mmap_sem * we will deadlock attempting to validate the fault against the * address space. Luckily the kernel only validly references user * space from well defined areas of code, which are listed in the
arch/powerpc/platforms/powermac/cpufreq_32.c renamed from arch/powerpc/platforms/powermac/cpufreq_32.c.old +1 -1
@@ -268,7 +268,7 @@/* Make sure the decrementer won't interrupt us */ asmvolatile ("mtdec %0" : :"r" (0x7fffffff )); -/* Make sure any pending DEC interrupt occuring while we did +/* Make sure any pending DEC interrupt occurring while we did * the above didn't re-enable the DEC */ mb (); asmvolatile ("mtdec %0" : :"r" (0x7fffffff ));
arch/powerpc/platforms/pseries/eeh_driver.c renamed from arch/powerpc/platforms/pseries/eeh_driver.c.old +1 -1
@@ -175,7 +175,7 @@* * pSeries systems will isolate a PCI slot if the PCI-Host * bridge detects address or data parity errors, DMA's -* occuring to wild addresses (which usually happen due to +* occurring to wild addresses (which usually happen due to * bugs in device drivers or in PCI adapter firmware). * Slot isolations also occur if #SERR, #PERR or other misc * PCI-related errors are detected.
arch/x86_64/mm/fault.c renamed from arch/x86_64/mm/fault.c.old +1 -1
@@ -418,7 +418,7 @@/* When running in the kernel we expect faults to occur only to * addresses in user space. All other faults represent errors in the * kernel and should generate an OOPS. Unfortunatly, in the case of an -* erroneous fault occuring in a code path which already holds mmap_sem +* erroneous fault occurring in a code path which already holds mmap_sem * we will deadlock attempting to validate the fault against the * address space. Luckily the kernel only validly references user * space from well defined areas of code, which are listed in the
drivers/infiniband/hw/ipath/ipath_intr.c renamed from drivers/infiniband/hw/ipath/ipath_intr.c.old +1 -1
@@ -397,7 +397,7 @@if ((dd->ipath_maskederrs & ~dd->ipath_ignorederrs) & ~(INFINIPATH_E_RRCVEGRFULL |INFINIPATH_E_RRCVHDRFULL ))ipath_dev_err (dd,"Disabling error(s) %llx because " -"occuring too frequently (%s)\n" , +"occurring too frequently (%s)\n" , (unsigned long long ) (dd->ipath_maskederrs & ~dd->ipath_ignorederrs), msg);
drivers/message/fusion/mptbase.c renamed from drivers/message/fusion/mptbase.c.old +1 -1
@@ -5593,7 +5593,7 @@/* The SCSI driver needs to adjust timeouts on all current * commands prior to the diagnostic reset being issued. -* Prevents timeouts occuring during a diagnostic reset...very bad. +* Prevents timeouts occurring during a diagnostic reset...very bad. * For all other protocol drivers, this is a no-op. */ {
drivers/net/wireless/ipw2100.c renamed from drivers/net/wireless/ipw2100.c.old +1 -1
@@ -5358,7 +5358,7 @@ idx, keylen, len);/* NOTE: We don't check cached values in case the firmware was reset -* or some other problem is occuring. If the user is setting the key, +* or some other problem is occurring. If the user is setting the key, * then we push the change */ wep_key->idx = idx;
drivers/serial/pxa.c renamed from drivers/serial/pxa.c.old +1 -1
@@ -390,7 +390,7 @@/* * Finally, enable interrupts. Note: Modem status interrupts -* are set via set_termios(), which will be occuring imminently +* are set via set_termios(), which will be occurring imminently * anyway, so we don't enable them here. */ up->ier =UART_IER_RLSI |UART_IER_RDI |UART_IER_RTOIE |UART_IER_UUE ;
include/asm-arm/thread_info.h renamed from include/asm-arm/thread_info.h.old +1 -1
@@ -110,7 +110,7 @@/* * We use bit 30 of the preempt_count to indicate that kernel -* preemption is occuring. See include/asm-arm/hardirq.h. +* preemption is occurring. See include/asm-arm/hardirq.h. */ #define PREEMPT_ACTIVE 0x40000000
include/asm-ia64/sn/tioca_provider.h renamed from include/asm-ia64/sn/tioca_provider.h.old +1 -1
@@ -27,7 +27,7 @@#define PV908234 (1 << 1)/* CA:AGPDMA write request data mismatch with ABC1CL merge */ #define PV895469 (1 << 1) -/* TIO:CA TLB invalidate of written GART entries possibly not occuring in CA*/ +/* TIO:CA TLB invalidate of written GART entries possibly not occurring in CA*/ #define PV910244 (1 << 1)struct tioca_dmamap {
kernel/cpuset.c renamed from kernel/cpuset.c.old +1 -1
@@ -1064,7 +1064,7 @@ }/* -* Frequency meter - How fast is some event occuring? +* Frequency meter - How fast is some event occurring? * * These routines manage a digitally filtered, constant time based, * event frequency meter. There are four routines: