leandrof/linux
1
0
Fork 0
forked from Minki/linux
Code Issues Pull Requests Packages Projects Releases Wiki Activity

typo fixes: occuring -> occurring

Browse Source 
Signed-off-by: Adrian Bunk <bunk@stusta.de>
This commit is contained in:
Adrian Bunk 2006-06-30 18:27:16 +02:00
parent 47bdd718c6
commit 80f7228b59
13 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/memory-barriers.txt
View File

@ -602,7 +602,7 @@ Consider the following sequence of events:
This sequence of events is committed to the memory coherence system in an order 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, 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
}: }:
+-------+ : : +-------+ : :

2
arch/i386/mm/fault.c
View File

@ -389,7 +389,7 @@ fastcall void __kprobes do_page_fault(struct pt_regs *regs,
/* When running in the kernel we expect faults to occur only to /* When running in the kernel we expect faults to occur only to
* addresses in user space. All other faults represent errors in the * addresses in user space. All other faults represent errors in the
* kernel and should generate an OOPS. Unfortunatly, in the case of an * 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 * we will deadlock attempting to validate the fault against the
* address space. Luckily the kernel only validly references user * address space. Luckily the kernel only validly references user
* space from well defined areas of code, which are listed in the * space from well defined areas of code, which are listed in the

2
arch/m32r/mm/fault.c
View File

@ -148,7 +148,7 @@ asmlinkage void do_page_fault(struct pt_regs *regs, unsigned long error_code,
/* When running in the kernel we expect faults to occur only to /* When running in the kernel we expect faults to occur only to
* addresses in user space. All other faults represent errors in the * addresses in user space. All other faults represent errors in the
* kernel and should generate an OOPS. Unfortunatly, in the case of an * 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 * we will deadlock attempting to validate the fault against the
* address space. Luckily the kernel only validly references user * address space. Luckily the kernel only validly references user
* space from well defined areas of code, which are listed in the * space from well defined areas of code, which are listed in the

2
arch/powerpc/platforms/powermac/cpufreq_32.c
View File

@ -268,7 +268,7 @@ static int pmu_set_cpu_speed(int low_speed)
/* Make sure the decrementer won't interrupt us */ /* Make sure the decrementer won't interrupt us */
asm volatile("mtdec %0" : : "r" (0x7fffffff)); asm volatile("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 */ * the above didn't re-enable the DEC */
mb(); mb();
asm volatile("mtdec %0" : : "r" (0x7fffffff)); asm volatile("mtdec %0" : : "r" (0x7fffffff));

2
arch/powerpc/platforms/pseries/eeh_driver.c
View File

@ -175,7 +175,7 @@ static void eeh_report_failure(struct pci_dev *dev, void *userdata)
* *
* pSeries systems will isolate a PCI slot if the PCI-Host * pSeries systems will isolate a PCI slot if the PCI-Host
* bridge detects address or data parity errors, DMA's * 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). * bugs in device drivers or in PCI adapter firmware).
* Slot isolations also occur if #SERR, #PERR or other misc * Slot isolations also occur if #SERR, #PERR or other misc
* PCI-related errors are detected. * PCI-related errors are detected.

2
arch/x86_64/mm/fault.c
View File

@ -418,7 +418,7 @@ asmlinkage void __kprobes do_page_fault(struct pt_regs *regs,
/* When running in the kernel we expect faults to occur only to /* When running in the kernel we expect faults to occur only to
* addresses in user space. All other faults represent errors in the * addresses in user space. All other faults represent errors in the
* kernel and should generate an OOPS. Unfortunatly, in the case of an * 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 * we will deadlock attempting to validate the fault against the
* address space. Luckily the kernel only validly references user * address space. Luckily the kernel only validly references user
* space from well defined areas of code, which are listed in the * space from well defined areas of code, which are listed in the

2
drivers/infiniband/hw/ipath/ipath_intr.c
View File

@ -397,7 +397,7 @@ static void handle_errors(struct ipath_devdata *dd, ipath_err_t errs)
if ((dd->ipath_maskederrs & ~dd->ipath_ignorederrs) & if ((dd->ipath_maskederrs & ~dd->ipath_ignorederrs) &
~(INFINIPATH_E_RRCVEGRFULL | INFINIPATH_E_RRCVHDRFULL)) ~(INFINIPATH_E_RRCVEGRFULL | INFINIPATH_E_RRCVHDRFULL))
ipath_dev_err(dd, "Disabling error(s) %llx because " ipath_dev_err(dd, "Disabling error(s) %llx because "
"occuring too frequently (%s)\n", "occurring too frequently (%s)\n",
(unsigned long long) (unsigned long long)
(dd->ipath_maskederrs & (dd->ipath_maskederrs &
~dd->ipath_ignorederrs), msg); ~dd->ipath_ignorederrs), msg);

2
drivers/message/fusion/mptbase.c
View File

@ -5592,7 +5592,7 @@ mpt_HardResetHandler(MPT_ADAPTER *ioc, int sleepFlag)
/* The SCSI driver needs to adjust timeouts on all current /* The SCSI driver needs to adjust timeouts on all current
* commands prior to the diagnostic reset being issued. * 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. * For all other protocol drivers, this is a no-op.
*/ */
{ {

2
drivers/net/wireless/ipw2100.c
View File

@ -5358,7 +5358,7 @@ static int ipw2100_set_key(struct ipw2100_priv *priv,
idx, keylen, len); idx, keylen, len);
/* NOTE: We don't check cached values in case the firmware was reset /* 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 */ * then we push the change */
wep_key->idx = idx; wep_key->idx = idx;

2
drivers/serial/pxa.c
View File

@ -390,7 +390,7 @@ static int serial_pxa_startup(struct uart_port *port)
/* /*
* Finally, enable interrupts. Note: Modem status interrupts * 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. * anyway, so we don't enable them here.
*/ */
up->ier = UART_IER_RLSI | UART_IER_RDI | UART_IER_RTOIE | UART_IER_UUE; up->ier = UART_IER_RLSI | UART_IER_RDI | UART_IER_RTOIE | UART_IER_UUE;

2
include/asm-arm/thread_info.h
View File

@ -116,7 +116,7 @@ extern void iwmmxt_task_release(struct thread_info *);
/* /*
* We use bit 30 of the preempt_count to indicate that kernel * 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 #define PREEMPT_ACTIVE 0x40000000

2
include/asm-ia64/sn/tioca_provider.h
View File

@ -27,7 +27,7 @@
#define PV908234 (1 << 1) #define PV908234 (1 << 1)
/* CA:AGPDMA write request data mismatch with ABC1CL merge */ /* CA:AGPDMA write request data mismatch with ABC1CL merge */
#define PV895469 (1 << 1) #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) #define PV910244 (1 << 1)
struct tioca_dmamap{ struct tioca_dmamap{

2
kernel/cpuset.c
View File

@ -1064,7 +1064,7 @@ static int update_flag(cpuset_flagbits_t bit, struct cpuset *cs, char *buf)
} }
/* /*
* 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, * These routines manage a digitally filtered, constant time based,
* event frequency meter. There are four routines: * event frequency meter. There are four routines: