[WATCHDOG] Kconfig typos fix.

Three typos in drivers/char/watchdog/Kconfig... Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com> Signed-off-by: Wim Van Sebroeck <wim@iguana.be>

[WATCHDOG] Kconfig typos fix.
Three typos in drivers/char/watchdog/Kconfig... Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com> Signed-off-by: Wim Van Sebroeck <wim@iguana.be>
Matt LaPlante · Wim Van Sebroeck
1 parent 9f737633e6
Showing 1 changed file with 4 additions and 4 deletions Side-by-side Diff
drivers/char/watchdog/Kconfig
@@ -45,7 +45,7 @@
 comment "Watchdog Device Drivers"
 	depends on WATCHDOG
  
-# Architecture Independant
+# Architecture Independent
  
 config SOFT_WATCHDOG
 	tristate "Software watchdog"
@@ -127,7 +127,7 @@
 	  enabled.
  
 	  The driver is limited by the speed of the system's PCLK
-	  signal, so with reasonbaly fast systems (PCLK around 50-66MHz)
+	  signal, so with reasonably fast systems (PCLK around 50-66MHz)
 	  then watchdog intervals of over approximately 20seconds are
 	  unavailable.
  
@@ -423,7 +423,7 @@
 	  is no way to know if writing to its IO address will corrupt
 	  your system or have any real effect.  The only way to be sure
 	  that this driver does what you want is to make sure you
-	  are runnning it on an EPX-C3 from Winsystems with the watchdog
+	  are running it on an EPX-C3 from Winsystems with the watchdog
 	  timer at IO address 0x1ee and 0x1ef.  It will write to both those
 	  IO ports.  Basically, the assumption is made that if you compile
 	  this driver into your kernel and/or load it as a module, that you
@@ -472,7 +472,7 @@
 	tristate "Indy/I2 Hardware Watchdog"
 	depends on WATCHDOG && SGI_IP22
 	help
-	  Hardwaredriver for the Indy's/I2's watchdog. This is a
+	  Hardware driver for the Indy's/I2's watchdog. This is a
 	  watchdog timer that will reboot the machine after a 60 second
 	  timer expired and no process has written to /dev/watchdog during
 	  that time.
...	...	@@ -45,7 +45,7 @@
45	45	comment "Watchdog Device Drivers"
46	46	depends on WATCHDOG
47	47
48		-# Architecture Independant
	48	+# Architecture Independent
49	49
50	50	config SOFT_WATCHDOG
51	51	tristate "Software watchdog"
...	...	@@ -127,7 +127,7 @@
127	127	enabled.
128	128
129	129	The driver is limited by the speed of the system's PCLK
130		- signal, so with reasonbaly fast systems (PCLK around 50-66MHz)
	130	+ signal, so with reasonably fast systems (PCLK around 50-66MHz)
131	131	then watchdog intervals of over approximately 20seconds are
132	132	unavailable.
133	133
...	...	@@ -423,7 +423,7 @@
423	423	is no way to know if writing to its IO address will corrupt
424	424	your system or have any real effect. The only way to be sure
425	425	that this driver does what you want is to make sure you
426		- are runnning it on an EPX-C3 from Winsystems with the watchdog
	426	+ are running it on an EPX-C3 from Winsystems with the watchdog
427	427	timer at IO address 0x1ee and 0x1ef. It will write to both those
428	428	IO ports. Basically, the assumption is made that if you compile
429	429	this driver into your kernel and/or load it as a module, that you
...	...	@@ -472,7 +472,7 @@
472	472	tristate "Indy/I2 Hardware Watchdog"
473	473	depends on WATCHDOG && SGI_IP22
474	474	help
475		- Hardwaredriver for the Indy's/I2's watchdog. This is a
	475	+ Hardware driver for the Indy's/I2's watchdog. This is a
476	476	watchdog timer that will reboot the machine after a 60 second
477	477	timer expired and no process has written to /dev/watchdog during
478	478	that time.