linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Soltysiak <solt@dns.toxicfilms.tv>
To: linux-kernel@vger.kernel.org
Subject: [TRIVIAL] 2 spelling patches in helps
Date: Tue, 5 Aug 2003 15:58:20 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.51.0308051556410.1321@dns.toxicfilms.tv> (raw)

Hi,

please consider these patches to fix spelling.

Regards,
Maciej Soltysiak

diff -u linux-2.6.0-test2/net/Kconfig linux-2.6.0-test2-mm4/net/Kconfig
--- linux-2.6.0-test2/net/Kconfig	2003-07-27 18:57:01.000000000 +0200
+++ linux-2.6.0-test2-mm4/net/Kconfig	2003-08-04 20:26:47.000000000 +0200
@@ -595,7 +602,7 @@
 	depends on EXPERIMENTAL
 	---help---
 	  This option enables NIC (Network Interface Card) hardware throttling
-	  during periods of extremal congestion. At the moment only a couple
+	  during periods of extreme congestion. At the moment only a couple
 	  of device drivers support it (really only one -- tulip, a modified
 	  8390 driver can be found at
 	  <ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz>).

diff -u linux-2.6.0-test2/Documentation/scsi/ncr53c8xx.txt linux-2.6.0-test2-mm4/Documentation/scsi/ncr53c8xx.txt
--- linux-2.6.0-test2/Documentation/scsi/ncr53c8xx.txt	2003-07-27 18:55:55.000000000 +0200
+++ linux-2.6.0-test2-mm4/Documentation/scsi/ncr53c8xx.txt	2003-08-04 20:27:40.000000000 +0200
@@ -1025,7 +1025,7 @@
 then it will for sure win the next SCSI BUS arbitration.

 Since, there is no way to know what devices are trying to arbitrate for the
-BUS, using this feature can be extremally unfair. So, you are not advised
+BUS, using this feature can be extremely unfair. So, you are not advised
 to enable it, or at most enable this feature for the case the chip lost
 the previous arbitration (boot option 'iarb:1').


                 reply	other threads:[~2003-08-05 13:58 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=Pine.LNX.4.51.0308051556410.1321@dns.toxicfilms.tv \
    --to=solt@dns.toxicfilms.tv \
    --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;
as well as URLs for NNTP newsgroup(s).