mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt LaPlante <laplam@rpi.edu>
To: linux-kernel@vger.kernel.org
Cc: trivial@kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [PATCH] Documentation/IPMI typos
Date: Thu, 29 Jun 2006 13:42:21 -0400	[thread overview]
Message-ID: <20060629134221.9460671e.laplam@rpi.edu> (raw)

Two typos in Documentation/IPMI...  Alan, if you could just verify the first please.

-- 
Matt LaPlante
CCNP, CCDP, A+, Linux+, CQS
laplam@rpi.edu

-

--- b/Documentation/IPMI.txt	2006-06-29 01:36:01.000000000 -0400
+++ a/Documentation/IPMI.txt	2006-06-29 01:40:21.000000000 -0400
@@ -10,7 +10,7 @@
 It provides for dynamic discovery of sensors in the system and the
 ability to monitor the sensors and be informed when the sensor's
 values change or go outside certain boundaries.  It also has a
-standardized database for field-replacable units (FRUs) and a watchdog
+standardized database for field-replaceable units (FRUs) and a watchdog
 timer.
 
 To use this, you need an interface to an IPMI controller in your
@@ -64,7 +64,7 @@
 IPMI defines a standard watchdog timer.  You can enable this with the
 'IPMI Watchdog Timer' config option.  If you compile the driver into
 the kernel, then via a kernel command-line option you can have the
-watchdog timer start as soon as it intitializes.  It also have a lot
+watchdog timer start as soon as it initializes.  It also have a lot
 of other options, see the 'Watchdog' section below for more details.
 Note that you can also have the watchdog continue to run if it is
 closed (by default it is disabled on close).  Go into the 'Watchdog


             reply	other threads:[~2006-06-29 17:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 17:42 Matt LaPlante [this message]
2006-06-29 21:57 ` 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=20060629134221.9460671e.laplam@rpi.edu \
    --to=laplam@rpi.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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

all inboxes | Powered by JetHome®