Commit 41d65010 authored by Michael Hayes's avatar Michael Hayes Committed by David Woodhouse

[PATCH] Spelling fixes - occurring

This fixes:
    occuring -> occurring

Fixes 29 occurrences in all.
parent 3e588d63
No related merge requests found
......@@ -296,7 +296,7 @@ static struct pci_ops iop310_secondary_ops = {
* within 3 instructions."
*
* This does not appear to be the case. With 8 NOPs after the load, we
* see the imprecise abort occuring on the STM of iop310_sec_pci_status()
* see the imprecise abort occurring on the STM of iop310_sec_pci_status()
* which is about 10 instructions away.
*
* Always trust reality!
......
......@@ -5113,7 +5113,7 @@ ate_freeze(pcibr_dmamap_t pcibr_dmamap,
/* Bridge Hardware Bug WAR #484930:
* Bridge can't handle updating External ATEs
* while DMA is occuring that uses External ATEs,
* while DMA is occurring that uses External ATEs,
* even if the particular ATEs involved are disjoint.
*/
......@@ -6844,7 +6844,7 @@ pcibr_xintr_preset(void *which_widget,
*
* This is the pcibr interrupt "wrapper" function that is called,
* in interrupt context, to initiate the interrupt handler(s) registered
* (via pcibr_intr_alloc/connect) for the occuring interrupt. Non-threaded
* (via pcibr_intr_alloc/connect) for the occurring interrupt. Non-threaded
* handlers will be called directly, and threaded handlers will have their
* thread woken up.
*/
......
......@@ -362,7 +362,7 @@ ate_freeze(pcibr_dmamap_t pcibr_dmamap,
/* Bridge Hardware Bug WAR #484930:
* Bridge can't handle updating External ATEs
* while DMA is occuring that uses External ATEs,
* while DMA is occurring that uses External ATEs,
* even if the particular ATEs involved are disjoint.
*/
......
......@@ -842,7 +842,7 @@ printk("pcibr_xintr_preset: b_wid_int_upper 0x%lx b_wid_int_lower 0x%lx b_int_ho
*
* This is the pcibr interrupt "wrapper" function that is called,
* in interrupt context, to initiate the interrupt handler(s) registered
* (via pcibr_intr_alloc/connect) for the occuring interrupt. Non-threaded
* (via pcibr_intr_alloc/connect) for the occurring interrupt. Non-threaded
* handlers will be called directly, and threaded handlers will have their
* thread woken up.
*/
......
......@@ -1556,7 +1556,7 @@ static uint32_t onyx_images[][PCXU_IMAGE_SIZE/sizeof(uint32_t)] = {
* IRTN_AV fires twice for every I-cache miss returning from RIB to the IFU.
* It will not fire if a second I-cache miss is issued from the IFU to RIB
* before the first returns. Therefore, if the IRTN_AV count is much less
* than 2x the ICORE_AV count, many speculative I-cache misses are occuring
* than 2x the ICORE_AV count, many speculative I-cache misses are occurring
* which are "discovered" to be incorrect fairly quickly.
* The ratio of I-cache miss transactions on Runway to the ICORE_AV count is
* a measure of the effectiveness of instruction prefetching. This ratio
......
......@@ -79,7 +79,7 @@ acpi_ev_initialize (
/*
* Initialize the Fixed and General Purpose acpi_events prior. This is
* done prior to enabling SCIs to prevent interrupts from occuring
* done prior to enabling SCIs to prevent interrupts from occurring
* before handers are installed.
*/
status = acpi_ev_fixed_event_initialize ();
......
......@@ -897,7 +897,7 @@ static int pc_write(struct tty_struct * tty, int from_user,
Remember copy_from_user WILL generate a page fault if the
user memory being accessed has been swapped out. This can
cause this routine to temporarily sleep while this page
fault is occuring.
fault is occurring.
----------------------------------------------------------------- */
......
......@@ -50,7 +50,7 @@
*
* Why `V' ? Well, `V' is the character in ASCII for the value 86,
* and we all know that 86 is _the_ most random number in the universe.
* Therefore it is the letter that has the slightest chance of occuring
* Therefore it is the letter that has the slightest chance of occurring
* by chance, when the system becomes corrupted.
*
*/
......
......@@ -175,7 +175,7 @@ static int wdt_status(void)
*
* Handle an interrupt from the board. These are raised when the status
* map changes in what the board considers an interesting way. That means
* a failure condition occuring.
* a failure condition occurring.
*/
void wdt_interrupt(int irq, void *dev_id, struct pt_regs *regs)
......
......@@ -158,7 +158,7 @@ static int wdtpci_status(void)
*
* Handle an interrupt from the board. These are raised when the status
* map changes in what the board considers an interesting way. That means
* a failure condition occuring.
* a failure condition occurring.
*/
static void wdtpci_interrupt(int irq, void *dev_id, struct pt_regs *regs)
......
......@@ -2066,7 +2066,7 @@ int __openfirmware powerbook_sleep_G3(void)
/* Make sure the decrementer won't interrupt us */
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 */
mb();
asm volatile("mtdec %0" : : "r" (0x7fffffff));
......@@ -2211,7 +2211,7 @@ int __openfirmware powerbook_sleep_Core99(void)
/* Make sure the decrementer won't interrupt us */
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 */
mb();
asm volatile("mtdec %0" : : "r" (0x7fffffff));
......@@ -2376,7 +2376,7 @@ int __openfirmware powerbook_sleep_3400(void)
/* Make sure the decrementer won't interrupt us */
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 */
mb();
asm volatile("mtdec %0" : : "r" (0x7fffffff));
......
......@@ -107,7 +107,7 @@
* the if clause for it(0,dev->tbusy)
* forever.
* The code got into this stage due to an
* interrupt occuring within the if clause for
* interrupt occurring within the if clause for
* set_bit(0,dev->tbusy). Since an interrupt
* disables furhter transmit interrupt and
* makes dev->tbusy = 0, this effect was undone
......
......@@ -2942,7 +2942,7 @@ static int check_singlebyte_msg(struct NCR_ESP *esp,
/* Target negotiates for synchronous transfers before we do, this
* is legal although very strange. What is even funnier is that
* the SCSI2 standard specifically recommends against targets doing
* this because so many initiators cannot cope with this occuring.
* this because so many initiators cannot cope with this occurring.
*/
static int target_with_ants_in_pants(struct NCR_ESP *esp,
Scsi_Cmnd *SCptr,
......
......@@ -3567,7 +3567,7 @@ static int check_singlebyte_msg(struct esp *esp)
/* Target negotiates for synchronous transfers before we do, this
* is legal although very strange. What is even funnier is that
* the SCSI2 standard specifically recommends against targets doing
* this because so many initiators cannot cope with this occuring.
* this because so many initiators cannot cope with this occurring.
*/
static int target_with_ants_in_pants(struct esp *esp,
Scsi_Cmnd *SCptr,
......
......@@ -3653,7 +3653,7 @@ static struct scripth scripth0 __initdata = {
** some target to reset or some disconnected
** job to abort. Since error recovery is a serious
** busyness, we will really reset the SCSI BUS, if
** case of a SCSI interrupt occuring in this path.
** case of a SCSI interrupt occurring in this path.
*/
/*
......
......@@ -1361,7 +1361,7 @@ static struct SYM_FWB_SCR SYM_FWB_SCR = {
* some target to reset or some disconnected
* job to abort. Since error recovery is a serious
* busyness, we will really reset the SCSI BUS, if
* case of a SCSI interrupt occuring in this path.
* case of a SCSI interrupt occurring in this path.
*/
#ifdef SYM_CONF_TARGET_ROLE_SUPPORT
......
......@@ -1246,7 +1246,7 @@ static struct SYM_FWB_SCR SYM_FWB_SCR = {
* some target to reset or some disconnected
* job to abort. Since error recovery is a serious
* busyness, we will really reset the SCSI BUS, if
* case of a SCSI interrupt occuring in this path.
* case of a SCSI interrupt occurring in this path.
*/
#ifdef SYM_CONF_TARGET_ROLE_SUPPORT
/*
......
......@@ -1241,7 +1241,7 @@ static int serial8250_startup(struct uart_port *port)
/*
* 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;
......
......@@ -713,7 +713,7 @@ static int sunsu_startup(struct uart_port *port)
/*
* 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;
......
......@@ -1381,7 +1381,7 @@ static int check_before_balancing (struct tree_balance * tb)
if ( cur_tb ) {
reiserfs_panic (tb->tb_sb, "vs-12335: check_before_balancing: "
"suspect that schedule occurred based on cur_tb not being null at this point in code. "
"do_balance cannot properly handle schedule occuring while it runs.");
"do_balance cannot properly handle schedule occurring while it runs.");
}
/* double check that buffers that we will modify are unlocked. (fix_nodes should already have
......
......@@ -2523,7 +2523,7 @@ int show_reiserfs_locks(void) {
** haven't hit disk yet. called from bitmap.c
**
** if it starts flushing things, it ors SCHEDULE_OCCURRED into repeat.
** note, this is just if schedule has a chance of occuring. I need to
** note, this is just if schedule has a chance of occurring. I need to
** change flush_commit_lists to have a repeat parameter too.
**
*/
......
......@@ -1495,7 +1495,7 @@ int reiserfs_cut_from_item (struct reiserfs_transaction_handle *th,
/* Repeat this loop until we either cut the item without needing
to balance, or we fix_nodes without schedule occuring */
to balance, or we fix_nodes without schedule occurring */
while ( 1 ) {
/* Determine the balance mode, position of the first byte to
be cut, and size to be cut. In case of the indirect item
......
......@@ -65,7 +65,7 @@ struct thread_struct {
/*
* At user->kernel entry, the pt_regs struct is stacked on the top of the kernel-stack.
* This macro allows us to find those regs for a task.
* Notice that subsequent pt_regs stackings, like recursive interrupts occuring while
* Notice that subsequent pt_regs stackings, like recursive interrupts occurring while
* we're in the kernel, won't affect this - only the first user->kernel transition
* registers are reached by this.
*/
......
......@@ -141,7 +141,7 @@ void pm_unregister_all(pm_callback callback)
* data field must hold the intended next state. No call is made
* if the state matches.
*
* BUGS: what stops two power management requests occuring in parallel
* BUGS: what stops two power management requests occurring in parallel
* and conflicting.
*
* WARNING: Calling pm_send directly is not generally recommended, in
......@@ -227,7 +227,7 @@ static void pm_undo_all(struct pm_dev *last)
* Zero is returned on success. If a suspend fails then the status
* from the device that vetoes the suspend is returned.
*
* BUGS: what stops two power management requests occuring in parallel
* BUGS: what stops two power management requests occurring in parallel
* and conflicting.
*/
......
......@@ -939,7 +939,7 @@ static int sctp_sf_send_restart_abort(union sctp_addr *ssa,
return 0;
}
/* A restart is occuring, check to make sure no new addresses
/* A restart is occurring, check to make sure no new addresses
* are being added as we may be under a takeover attack.
*/
static int sctp_sf_check_restart_addrs(const sctp_association_t *new_asoc,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment