Re: [PATCH] trivial: fix typos "ass?o[sc]iac?te" -> "associate"

From: Jiri Kosina
Date: Mon Feb 15 2010 - 09:32:26 EST


On Fri, 12 Feb 2010, Uwe Kleine-KÃnig wrote:

> This patch was generated by
>
> git grep -l -i -z -E '\<a[cs][cs]?o[sc]i[ae]c?te' | xargs -0 -r perl -p -i -e 's/\b([Aa])[cs][cs]?o[sc]i[ae]c?te/$1ssociate/'
>
> Signed-off-by: Uwe Kleine-KÃnig <u.kleine-koenig@xxxxxxxxxxxxxx>
> ---
> drivers/usb/musb/davinci.c | 2 +-
> drivers/zorro/zorro.ids | 2 +-
> include/net/irda/irttp.h | 2 +-
> kernel/irq/chip.c | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/musb/davinci.c b/drivers/usb/musb/davinci.c
> index 6691381..a883f9d 100644
> --- a/drivers/usb/musb/davinci.c
> +++ b/drivers/usb/musb/davinci.c
> @@ -274,7 +274,7 @@ static irqreturn_t davinci_interrupt(int irq, void *__hci)
> /* NOTE: DaVinci shadows the Mentor IRQs. Don't manage them through
> * the Mentor registers (except for setup), use the TI ones and EOI.
> *
> - * Docs describe irq "vector" registers asociated with the CPPI and
> + * Docs describe irq "vector" registers associated with the CPPI and
> * USB EOI registers. These hold a bitmask corresponding to the
> * current IRQ, not an irq handler address. Would using those bits
> * resolve some of the races observed in this dispatch code??
> diff --git a/drivers/zorro/zorro.ids b/drivers/zorro/zorro.ids
> index 0c0f99e..de24e3d 100644
> --- a/drivers/zorro/zorro.ids
> +++ b/drivers/zorro/zorro.ids
> @@ -108,7 +108,7 @@
> 0c00 500XP/SupraDrive WordSync [SCSI Host Adapter]
> 0d00 SupraDrive WordSync II [SCSI Host Adapter]
> 1000 2400zi+ [Modem]
> -0422 Computer Systems Assosiates
> +0422 Computer Systems Associates
> 1100 Magnum 40 [Accelerator and SCSI Host Adapter]
> 1500 12 Gauge [SCSI Host Adapter]
> 0439 Marc Michael Groth
> diff --git a/include/net/irda/irttp.h b/include/net/irda/irttp.h
> index 0788c23..11aee7a 100644
> --- a/include/net/irda/irttp.h
> +++ b/include/net/irda/irttp.h
> @@ -97,7 +97,7 @@
> #define TTP_MAX_SDU_SIZE 0x01
>
> /*
> - * This structure contains all data assosiated with one instance of a TTP
> + * This structure contains all data associated with one instance of a TTP
> * connection.
> */
> struct tsap_cb {
> diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
> index ecc3fa2..ec8a963 100644
> --- a/kernel/irq/chip.c
> +++ b/kernel/irq/chip.c
> @@ -520,7 +520,7 @@ out:
> * signal. The occurence is latched into the irq controller hardware
> * and must be acked in order to be reenabled. After the ack another
> * interrupt can happen on the same source even before the first one
> - * is handled by the assosiacted event handler. If this happens it
> + * is handled by the associated event handler. If this happens it
> * might be necessary to disable (mask) the interrupt depending on the
> * controller hardware. This requires to reenable the interrupt inside
> * of the loop which handles the interrupts which have arrived while

Applied, thanks.

--
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/