Skip to contentSkip to conversation

typo fixes: specfic -> specific

PATCH New Adrian Bunk 1 participant 1 message Jun 28, 2006

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 typo fixes: specfic -> specific

---

 arch/i386/mm/discontig.c                |    2 +-
 include/asm-arm/arch-at91rm9200/board.h |    2 +-
 sound/sparc/dbri.c                      |    2 +-
 usr/klibc/zlib/FAQ                      |    2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)
arch/i386/mm/discontig.c renamed from arch/i386/mm/discontig.c.old +1 -1
@@ -43,7 +43,7 @@
 bootmem_data_t node0_bdata;
 
 /*
- * numa interface - we expect the numa architecture specfic code to have
+ * numa interface - we expect the numa architecture specific code to have
  *                  populated the following initialisation.
  *
  * 1) node_online_map  - the map of all nodes configured (online) in the system
include/asm-arm/arch-at91rm9200/board.h renamed from include/asm-arm/arch-at91rm9200/board.h.old +1 -1
@@ -20,7 +20,7 @@
 
 /*
  * These are data structures found in platform_device.dev.platform_data,
- * and describing board-specfic data needed by drivers.  For example,
+ * and describing board-specific data needed by drivers.  For example,
  * which pin is used for a given GPIO role.
  *
  * In 2.6, drivers should strongly avoid board-specific knowledge so
sound/sparc/dbri.c renamed from sound/sparc/dbri.c.old +1 -1
@@ -46,7 +46,7 @@
  *
  * I've tried to stick to the following function naming conventions:
  * snd_*	ALSA stuff
- * cs4215_*	CS4215 codec specfic stuff
+ * cs4215_*	CS4215 codec specific stuff
  * dbri_*	DBRI high-level stuff
  * other	DBRI low-level stuff
  */
usr/klibc/zlib/FAQ renamed from usr/klibc/zlib/FAQ.old +1 -1
@@ -318,7 +318,7 @@
     correctly points to the zlib specification in RFC 1950 for the "deflate"
     transfer encoding, there have been reports of servers and browsers that
     incorrectly produce or expect raw deflate data per the deflate
-    specficiation in RFC 1951, most notably Microsoft. So even though the
+    specificiation in RFC 1951, most notably Microsoft. So even though the
     "deflate" transfer encoding using the zlib format would be the more
     efficient approach (and in fact exactly what the zlib format was designed
     for), using the "gzip" transfer encoding is probably more reliable due to