All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org
Subject: Re: [PATCH] include/asm-mips/: Spelling fixes
Date: Mon, 17 Dec 2007 12:02:09 -0800	[thread overview]
Message-ID: <1197921729.27386.13.camel@localhost> (raw)
In-Reply-To: <4766D3BE.7070509@ru.mvista.com>

On Mon, 2007-12-17 at 22:53 +0300, Sergei Shtylyov wrote:
> > - * PCI interrupts will come in on either the INTA or INTD interrups lines,
> > + * PCI interrupts will come in on either the INTA or INTD interrupts lines,
>     "interrupt" here.

Quite right.
I did them by script and inspected, but didn't notice that one.
cheers, Joe

Signed-off-by: Joe Perches <joe@perches.com>
---
diff --git a/include/asm-mips/mach-wrppmc/mach-gt64120.h b/include/asm-mips/mach-wrppmc/mach-gt64120.h
index 00d8bf6..465234a 100644
--- a/include/asm-mips/mach-wrppmc/mach-gt64120.h
+++ b/include/asm-mips/mach-wrppmc/mach-gt64120.h
@@ -45,7 +45,7 @@
 #define GT_PCI_IO_SIZE	0x02000000UL
 
 /*
- * PCI interrupts will come in on either the INTA or INTD interrups lines,
+ * PCI interrupts will come in on either the INTA or INTD interrupt lines,
  * which are mapped to the #2 and #5 interrupt pins of the MIPS.  On our
  * boards, they all either come in on IntD or they all come in on IntA, they
  * aren't mixed. There can be numerous PCI interrupts, so we keep a list of the

  reply	other threads:[~2007-12-17 20:02 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 19:30 [PATCH] arch/sparc64/: Spelling fixes Joe Perches
2007-12-17 19:30 ` [PATCH] include/asm-mips/: " Joe Perches
2007-12-17 19:53   ` Sergei Shtylyov
2007-12-17 20:02     ` Joe Perches [this message]
2007-12-17 19:30 ` [PATCH] arch/powerpc/: " Joe Perches
2007-12-17 19:30   ` Joe Perches
2007-12-17 19:36   ` Josh Boyer
2007-12-17 19:36     ` Josh Boyer
2007-12-17 19:30 ` [PATCH] include/asm-powerpc/: " Joe Perches
2007-12-17 19:30   ` Joe Perches
2007-12-17 19:30 ` [PATCH] arch/ppc/: " Joe Perches
2007-12-17 19:30   ` Joe Perches
2007-12-17 20:42   ` Vitaly Bordug
2007-12-17 20:42     ` Vitaly Bordug
2007-12-17 20:52     ` Joe Perches
2007-12-17 20:52       ` Joe Perches
2007-12-17 19:30 ` [PATCH] include/asm-ppc/: " Joe Perches
2007-12-17 19:30   ` Joe Perches
2007-12-17 19:30 ` [PATCH] arch/s390/: " Joe Perches
2007-12-17 19:30 ` [PATCH] include/asm-s390/: " Joe Perches
2007-12-17 19:30 ` [PATCH] arch/sh/: " Joe Perches
2007-12-17 19:30 ` [PATCH] include/asm-sh/: " Joe Perches
2007-12-17 19:30 ` [PATCH] arch/sh64/: " Joe Perches
2007-12-17 19:30 ` [PATCH] arch/sparc/: " Joe Perches
2007-12-20 21:55   ` David Miller
2007-12-20 21:55     ` David Miller
2007-12-17 19:30 ` [PATCH] arch/sparc64/: " Joe Perches
2007-12-20 21:55   ` David Miller
2007-12-20 21:55     ` David Miller
2007-12-17 19:30 ` [uml-devel] [PATCH] arch/um: " Joe Perches
2007-12-17 19:30   ` Joe Perches
2007-12-17 19:30 ` [PATCH] arch/x86/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/acpi/: " Joe Perches
2007-12-17 19:30 ` [PATCH] include/acpi/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/ata/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/atm/: " Joe Perches
2007-12-20 22:05   ` David Miller
2007-12-17 19:30 ` [PATCH] drivers/block/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/bluetooth/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/char/: " Joe Perches
2007-12-17 23:11 ` [PATCH] arch/sh/: " Paul Mundt
2007-12-18  7:07 ` [PATCH] include/asm-parisc/: " Grant Grundler
2007-12-18 10:04 ` [PATCH] arch/s390/: " Martin Schwidefsky
2007-12-18 13:01 ` [PATCH] arch/x86/: " Ingo Molnar
2008-01-07 20:07 ` [PATCH] drivers/block/: " Miller, Mike (OS Dev)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1197921729.27386.13.camel@localhost \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=sshtylyov@ru.mvista.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.