mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael-lists@free-electrons.com>
To: linux-kernel@vger.kernel.org
Cc: trivial@kernel.org
Subject: [PATCH 2.16.18] [TRIVIAL] Spelling fix: "control" instead of "cotrol"
Date: Thu, 21 Sep 2006 13:20:11 +0200	[thread overview]
Message-ID: <200609211320.13040.michael-lists@free-electrons.com> (raw)

This patch against Linux 2.6.18 fixes a spelling mistake happening
in the below files ("control" instead of "cotrol")

drivers/net/ne2.c: * bit by bit.  The EEPROM cotrol port at base + 0x1e has 
the following
mm/nommu.c: *   For tight cotrol over page level allocator and protection 
flags
mm/vmalloc.c: * For tight cotrol over page level allocator and protection 
flags
mm/vmalloc.c: * For tight cotrol over page level allocator and protection 
flags
mm/vmalloc.c: * For tight cotrol over page level allocator and protection 
flags

Such comments and spelling mistakes then show up in the automatically 
generated kernel documentation (created by "make htmldocs").

	Michael.

--

Signed-off-by: Michael Opdenacker <michael@free-electrons.com>

diff -Nurp linux-2.6.18/drivers/net/ne2.c 
linux-2.6.18-spelling1/drivers/net/ne2.c
--- linux-2.6.18/drivers/net/ne2.c	2006-09-20 05:42:06.000000000 +0200
+++ linux-2.6.18-spelling1/drivers/net/ne2.c	2006-09-21 13:07:24.000000000 
+0200
@@ -152,7 +152,7 @@ static void ne_block_output(struct net_d
 /*
  * special code to read the DE-320's MAC address EEPROM.  In contrast to a 
  * standard NE design, this is a serial EEPROM (93C46) that has to be read
- * bit by bit.  The EEPROM cotrol port at base + 0x1e has the following 
+ * bit by bit.  The EEPROM control port at base + 0x1e has the following 
  * layout:
  *
  * Bit 0 = Data out (read from EEPROM)
diff -Nurp linux-2.6.18/mm/nommu.c linux-2.6.18-spelling1/mm/nommu.c
--- linux-2.6.18/mm/nommu.c	2006-09-20 05:42:06.000000000 +0200
+++ linux-2.6.18-spelling1/mm/nommu.c	2006-09-21 13:07:36.000000000 +0200
@@ -197,7 +197,7 @@ long vwrite(char *buf, char *addr, unsig
  *	Allocate enough pages to cover @size from the page level
  *	allocator and map them into continguos kernel virtual space.
  *
- *	For tight cotrol over page level allocator and protection flags
+ *	For tight control over page level allocator and protection flags
  *	use __vmalloc() instead.
  */
 void *vmalloc(unsigned long size)
diff -Nurp linux-2.6.18/mm/vmalloc.c linux-2.6.18-spelling1/mm/vmalloc.c
--- linux-2.6.18/mm/vmalloc.c	2006-09-20 05:42:06.000000000 +0200
+++ linux-2.6.18-spelling1/mm/vmalloc.c	2006-09-21 13:07:59.000000000 +0200
@@ -509,7 +509,7 @@ EXPORT_SYMBOL(__vmalloc);
  *	Allocate enough pages to cover @size from the page level
  *	allocator and map them into contiguous kernel virtual space.
  *
- *	For tight cotrol over page level allocator and protection flags
+ *	For tight control over page level allocator and protection flags
  *	use __vmalloc() instead.
  */
 void *vmalloc(unsigned long size)
@@ -549,7 +549,7 @@ EXPORT_SYMBOL(vmalloc_user);
  *	Allocate enough pages to cover @size from the page level
  *	allocator and map them into contiguous kernel virtual space.
  *
- *	For tight cotrol over page level allocator and protection flags
+ *	For tight control over page level allocator and protection flags
  *	use __vmalloc() instead.
  */
 void *vmalloc_node(unsigned long size, int node)
@@ -571,7 +571,7 @@ EXPORT_SYMBOL(vmalloc_node);
  *	the page level allocator and map them into contiguous and
  *	executable kernel virtual space.
  *
- *	For tight cotrol over page level allocator and protection flags
+ *	For tight control over page level allocator and protection flags
  *	use __vmalloc() instead.
  */
 

-- 
Michael Opdenacker, Free Electrons
Free Embedded Linux Training Materials
on http://free-electrons.com/training
(More than 1000 pages!)

             reply	other threads:[~2006-09-21 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21 11:20 Michael Opdenacker [this message]
2006-09-21 15:59 ` Alan Cox

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=200609211320.13040.michael-lists@free-electrons.com \
    --to=michael-lists@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@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

Powered by JetHome