Commit d1e76fee authored by Michael Hayes's avatar Michael Hayes Committed by Linus Torvalds

[PATCH] Spelling fixes: weird

    wierd -> weird
    wierdo -> weirdo
    wierdness -> weirdness
parent 09c49f76
...@@ -291,7 +291,7 @@ void M68360_do_irq(int vec, struct pt_regs *fp) ...@@ -291,7 +291,7 @@ void M68360_do_irq(int vec, struct pt_regs *fp)
/* unsigned long pend = *(volatile unsigned long *)pquicc->intr_cipr; */ /* unsigned long pend = *(volatile unsigned long *)pquicc->intr_cipr; */
/* Bugger all that wierdness. For the moment, I seem to know where I came from; /* Bugger all that weirdness. For the moment, I seem to know where I came from;
* vec is passed from a specific ISR, so I'll use it. */ * vec is passed from a specific ISR, so I'll use it. */
if (int_irq_list[irq] && int_irq_list[irq]->handler) { if (int_irq_list[irq] && int_irq_list[irq]->handler) {
......
...@@ -67,7 +67,7 @@ void __init multi_init (void) ...@@ -67,7 +67,7 @@ void __init multi_init (void)
if ((word & 0xFC0) == 0x780) { if ((word & 0xFC0) == 0x780) {
/* A `jr' insn, fix up its offset (and yes, the /* A `jr' insn, fix up its offset (and yes, the
wierd half-word swapping is intentional). */ weird half-word swapping is intentional). */
unsigned short hi = word & 0xFFFF; unsigned short hi = word & 0xFFFF;
unsigned short lo = word >> 16; unsigned short lo = word >> 16;
unsigned long udisp22 unsigned long udisp22
......
...@@ -828,7 +828,7 @@ static phy_info_t phy_info_lxt970 = { ...@@ -828,7 +828,7 @@ static phy_info_t phy_info_lxt970 = {
/* /*
* I had some nice ideas of running the MDIO faster... * I had some nice ideas of running the MDIO faster...
* The 971 should support 8MHz and I tried it, but things acted really * The 971 should support 8MHz and I tried it, but things acted really
* wierd, so 2.5 MHz ought to be enough for anyone... * weird, so 2.5 MHz ought to be enough for anyone...
*/ */
static void mii_parse_lxt971_sr2(uint mii_reg, struct net_device *dev) static void mii_parse_lxt971_sr2(uint mii_reg, struct net_device *dev)
......
...@@ -60,7 +60,7 @@ ...@@ -60,7 +60,7 @@
#define CO_APIC_PCIA_BASE0 0 /* and 1 */ /* slot 0, line 0 */ #define CO_APIC_PCIA_BASE0 0 /* and 1 */ /* slot 0, line 0 */
#define CO_APIC_PCIA_BASE123 5 /* and 6 */ /* slot 0, line 1 */ #define CO_APIC_PCIA_BASE123 5 /* and 6 */ /* slot 0, line 1 */
#define CO_APIC_PIIX4_USB 7 /* this one is wierd */ #define CO_APIC_PIIX4_USB 7 /* this one is weird */
/* Lithium PCI Bridge B -- "the one with PIIX4" */ /* Lithium PCI Bridge B -- "the one with PIIX4" */
#define CO_APIC_PCIB_BASE0 8 /* and 9-12 *//* slot 0, line 0 */ #define CO_APIC_PCIB_BASE0 8 /* and 9-12 *//* slot 0, line 0 */
......
...@@ -22,7 +22,7 @@ ...@@ -22,7 +22,7 @@
#define PLATFORM_LONG "GDB V850E simulator" #define PLATFORM_LONG "GDB V850E simulator"
/* We use a wierd value for RAM, not just 0, for testing purposes. /* We use a weird value for RAM, not just 0, for testing purposes.
These must match the values used in the linker script. */ These must match the values used in the linker script. */
#define RAM_ADDR 0x8F000000 #define RAM_ADDR 0x8F000000
#define RAM_SIZE 0x01000000 #define RAM_SIZE 0x01000000
......
...@@ -687,7 +687,7 @@ typedef struct wf_fx_info { ...@@ -687,7 +687,7 @@ typedef struct wf_fx_info {
/* Allow direct user-space control over FX memory/coefficient data. /* Allow direct user-space control over FX memory/coefficient data.
In theory this could be used to download the FX microprogram, In theory this could be used to download the FX microprogram,
but it would be a little slower, and involve some wierd code. but it would be a little slower, and involve some weird code.
*/ */
#define WFFX_MEMSET 69 #define WFFX_MEMSET 69
......
...@@ -227,7 +227,7 @@ snd_wavefront_fx_ioctl (snd_hwdep_t *sdev, struct file *file, ...@@ -227,7 +227,7 @@ snd_wavefront_fx_ioctl (snd_hwdep_t *sdev, struct file *file,
This code was developed using DOSEMU. The Turtle Beach SETUPSND This code was developed using DOSEMU. The Turtle Beach SETUPSND
utility was run with I/O tracing in DOSEMU enabled, and a reconstruction utility was run with I/O tracing in DOSEMU enabled, and a reconstruction
of the port I/O done, using the Yamaha faxback document as a guide of the port I/O done, using the Yamaha faxback document as a guide
to add more logic to the code. Its really pretty wierd. to add more logic to the code. Its really pretty weird.
There was an alternative approach of just dumping the whole I/O There was an alternative approach of just dumping the whole I/O
sequence as a series of port/value pairs and a simple loop sequence as a series of port/value pairs and a simple loop
...@@ -692,7 +692,7 @@ snd_wavefront_fx_start (snd_wavefront_t *dev) ...@@ -692,7 +692,7 @@ snd_wavefront_fx_start (snd_wavefront_t *dev)
return (0); return (0);
} }
/* wierd stuff, derived from port I/O tracing with dosemu */ /* weird stuff, derived from port I/O tracing with dosemu */
static unsigned char page_zero[] __initdata = { static unsigned char page_zero[] __initdata = {
0x01, 0x7c, 0x00, 0x1e, 0x00, 0x00, 0x00, 0x00, 0x00, 0xf5, 0x00, 0x01, 0x7c, 0x00, 0x1e, 0x00, 0x00, 0x00, 0x00, 0x00, 0xf5, 0x00,
......
...@@ -518,7 +518,7 @@ snd_wavefront_cmd (snd_wavefront_t *dev, ...@@ -518,7 +518,7 @@ snd_wavefront_cmd (snd_wavefront_t *dev,
/*********************************************************************** /***********************************************************************
WaveFront data munging WaveFront data munging
Things here are wierd. All data written to the board cannot Things here are weird. All data written to the board cannot
have its most significant bit set. Any data item with values have its most significant bit set. Any data item with values
potentially > 0x7F (127) must be split across multiple bytes. potentially > 0x7F (127) must be split across multiple bytes.
...@@ -527,7 +527,7 @@ the x86 side as 8-32 bit values. Sometimes, we need to munge data ...@@ -527,7 +527,7 @@ the x86 side as 8-32 bit values. Sometimes, we need to munge data
that is represented on the x86 side as an array of bytes. The most that is represented on the x86 side as an array of bytes. The most
efficient approach to handling both cases seems to be to use 2 efficient approach to handling both cases seems to be to use 2
different functions for munging and 2 for de-munging. This avoids different functions for munging and 2 for de-munging. This avoids
wierd casting and worrying about bit-level offsets. weird casting and worrying about bit-level offsets.
**********************************************************************/ **********************************************************************/
...@@ -1034,7 +1034,7 @@ wavefront_send_sample (snd_wavefront_t *dev, ...@@ -1034,7 +1034,7 @@ wavefront_send_sample (snd_wavefront_t *dev,
shptr = munge_int32 (*((u32 *) &header->hdr.s.sampleEndOffset), shptr = munge_int32 (*((u32 *) &header->hdr.s.sampleEndOffset),
shptr, 4); shptr, 4);
/* This one is truly wierd. What kind of wierdo decided that in /* This one is truly weird. What kind of weirdo decided that in
a system dominated by 16 and 32 bit integers, they would use a system dominated by 16 and 32 bit integers, they would use
a just 12 bits ? a just 12 bits ?
*/ */
......
...@@ -1212,7 +1212,7 @@ static int sq_ioctl(struct inode *inode, struct file *file, u_int cmd, ...@@ -1212,7 +1212,7 @@ static int sq_ioctl(struct inode *inode, struct file *file, u_int cmd,
return result ; return result ;
break ; break ;
case SNDCTL_DSP_SPEED: case SNDCTL_DSP_SPEED:
/* changing this on the fly will have wierd effects on the sound. /* changing this on the fly will have weird effects on the sound.
Where there are rate conversions implemented in soft form - it Where there are rate conversions implemented in soft form - it
will cause the _ctx_xxx() functions to be substituted. will cause the _ctx_xxx() functions to be substituted.
However, there doesn't appear to be any reason to dis-allow it from However, there doesn't appear to be any reason to dis-allow it from
......
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