From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Subject: [2.6 patch] typo fixes: disadvantadge -> disadvantage
Date: Wed, 28 Jun 2006 18:55:07 +0200 [thread overview]
Message-ID: <20060628165507.GY13915@stusta.de> (raw)
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
Documentation/arm/IXP4xx | 2 +-
include/asm-arm/arch-ixp4xx/io.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.17-mm3-full/Documentation/arm/IXP4xx.old 2006-06-27 20:44:39.000000000 +0200
+++ linux-2.6.17-mm3-full/Documentation/arm/IXP4xx 2006-06-27 20:44:58.000000000 +0200
@@ -85,7 +85,7 @@
2) If > 64MB of memory space is required, the IXP4xx can be
configured to use indirect registers to access PCI This allows
for up to 128MB (0x48000000 to 0x4fffffff) of memory on the bus.
- The disadvantadge of this is that every PCI access requires
+ The disadvantage of this is that every PCI access requires
three local register accesses plus a spinlock, but in some
cases the performance hit is acceptable. In addition, you cannot
mmap() PCI devices in this case due to the indirect nature
--- linux-2.6.17-mm3-full/include/asm-arm/arch-ixp4xx/io.h.old 2006-06-27 20:45:06.000000000 +0200
+++ linux-2.6.17-mm3-full/include/asm-arm/arch-ixp4xx/io.h 2006-06-27 20:45:09.000000000 +0200
@@ -38,7 +38,7 @@
* 2) If > 64MB of memory space is required, the IXP4xx can be configured
* to use indirect registers to access PCI (as we do below for I/O
* transactions). This allows for up to 128MB (0x48000000 to 0x4fffffff)
- * of memory on the bus. The disadvantadge of this is that every
+ * of memory on the bus. The disadvantage of this is that every
* PCI access requires three local register accesses plus a spinlock,
* but in some cases the performance hit is acceptable. In addition,
* you cannot mmap() PCI devices in this case.
reply other threads:[~2006-06-28 17:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060628165507.GY13915@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox