From: Matt LaPlante <laplam@rpi.edu>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: [PATCH] KConfig: Spellchecking 'similarity' and 'independent'
Date: Thu, 29 Jun 2006 01:32:47 -0400 [thread overview]
Message-ID: <20060629013247.c301a5ba.laplam@rpi.edu> (raw)
Several KConfig files had 'similarity' and 'independent' spelled incorrectly...
-
Matt LaPlante
CCNP, CCDP, A+, Linux+, CQS
laplam@rpi.edu
--
diff -ru a/arch/i386/Kconfig b/arch/i386/Kconfig
--- a/arch/i386/Kconfig 2006-06-29 00:23:23.000000000 -0400
+++ b/arch/i386/Kconfig 2006-06-29 00:40:56.000000000 -0400
@@ -737,7 +737,7 @@
but it is independent of the system firmware. And like a reboot
you can start any kernel with it, not just Linux.
- The name comes from the similiarity to the exec system call.
+ The name comes from the similarity to the exec system call.
It is an ongoing process to be certain the hardware in a machine
is properly shutdown, so do not be surprised if this code does not
diff -ru a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
--- a/arch/powerpc/Kconfig 2006-06-29 00:23:24.000000000 -0400
+++ b/arch/powerpc/Kconfig 2006-06-29 00:40:56.000000000 -0400
@@ -624,10 +624,10 @@
help
kexec is a system call that implements the ability to shutdown your
current kernel, and to start another kernel. It is like a reboot
- but it is indepedent of the system firmware. And like a reboot
+ but it is independent of the system firmware. And like a reboot
you can start any kernel with it, not just Linux.
- The name comes from the similiarity to the exec system call.
+ The name comes from the similarity to the exec system call.
It is an ongoing process to be certain the hardware in a machine
is properly shutdown, so do not be surprised if this code does not
diff -ru a/arch/ppc/Kconfig b/arch/ppc/Kconfig
--- a/arch/ppc/Kconfig 2006-06-29 00:23:24.000000000 -0400
+++ b/arch/ppc/Kconfig 2006-06-29 00:40:56.000000000 -0400
@@ -219,10 +219,10 @@
help
kexec is a system call that implements the ability to shutdown your
current kernel, and to start another kernel. It is like a reboot
- but it is indepedent of the system firmware. And like a reboot
+ but it is independent of the system firmware. And like a reboot
you can start any kernel with it, not just Linux.
- The name comes from the similiarity to the exec system call.
+ The name comes from the similarity to the exec system call.
It is an ongoing process to be certain the hardware in a machine
is properly shutdown, so do not be surprised if this code does not
diff -ru a/arch/sh/Kconfig b/arch/sh/Kconfig
--- a/arch/sh/Kconfig 2006-06-20 05:31:55.000000000 -0400
+++ b/arch/sh/Kconfig 2006-06-29 00:40:56.000000000 -0400
@@ -465,10 +465,10 @@
help
kexec is a system call that implements the ability to shutdown your
current kernel, and to start another kernel. It is like a reboot
- but it is indepedent of the system firmware. And like a reboot
+ but it is independent of the system firmware. And like a reboot
you can start any kernel with it, not just Linux.
- The name comes from the similiarity to the exec system call.
+ The name comes from the similarity to the exec system call.
It is an ongoing process to be certain the hardware in a machine
is properly shutdown, so do not be surprised if this code does not
diff -ru a/arch/x86_64/Kconfig b/arch/x86_64/Kconfig
--- a/arch/x86_64/Kconfig 2006-06-29 00:23:24.000000000 -0400
+++ b/arch/x86_64/Kconfig 2006-06-29 00:40:56.000000000 -0400
@@ -459,10 +459,10 @@
help
kexec is a system call that implements the ability to shutdown your
current kernel, and to start another kernel. It is like a reboot
- but it is indepedent of the system firmware. And like a reboot
+ but it is independent of the system firmware. And like a reboot
you can start any kernel with it, not just Linux.
- The name comes from the similiarity to the exec system call.
+ The name comes from the similarity to the exec system call.
It is an ongoing process to be certain the hardware in a machine
is properly shutdown, so do not be surprised if this code does not
next reply other threads:[~2006-06-29 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 5:32 Matt LaPlante [this message]
2006-06-29 12:10 ` [PATCH] KConfig: Spellchecking 'similarity' and 'independent' 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=20060629013247.c301a5ba.laplam@rpi.edu \
--to=laplam@rpi.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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