Hi all, Andrew,
Typo fix: explictly -> explicitly.
Signed-off-by: Jean Delvare <[email protected]>
Documentation/cpusets.txt | 2 +-
drivers/char/cyclades.c | 2 +-
drivers/scsi/mesh.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--- linux-2.6.14-rc2.orig/Documentation/cpusets.txt 2005-09-13 21:20:57.000000000 +0200
+++ linux-2.6.14-rc2/Documentation/cpusets.txt 2005-09-25 17:02:19.000000000 +0200
@@ -94,7 +94,7 @@
But larger systems, which benefit more from careful processor and
memory placement to reduce memory access times and contention,
and which typically represent a larger investment for the customer,
-can benefit from explictly placing jobs on properly sized subsets of
+can benefit from explicitly placing jobs on properly sized subsets of
the system.
This can be especially valuable on:
--- linux-2.6.14-rc2.orig/drivers/char/cyclades.c 2005-09-13 21:21:05.000000000 +0200
+++ linux-2.6.14-rc2/drivers/char/cyclades.c 2005-09-25 17:02:28.000000000 +0200
@@ -281,7 +281,7 @@
* make sure "cyc" appears in all kernel messages; all soft interrupts
* handled by same routine; recognize out-of-band reception; comment
* out some diagnostic messages; leave RTS/CTS flow control to hardware;
- * fix race condition in -Z buffer management; only -Y needs to explictly
+ * fix race condition in -Z buffer management; only -Y needs to explicitly
* flush chars; tidy up some startup messages;
*
* Revision 1.36.4.18 1996/07/25 18:57:31 bentson
--- linux-2.6.14-rc2.orig/drivers/scsi/mesh.c 2005-09-13 21:21:12.000000000 +0200
+++ linux-2.6.14-rc2/drivers/scsi/mesh.c 2005-09-25 17:02:25.000000000 +0200
@@ -730,7 +730,7 @@
* issue a SEQ_MSGOUT to get the mesh to drop ACK.
*/
if ((in_8(&mr->bus_status0) & BS0_ATN) == 0) {
- dlog(ms, "bus0 was %.2x explictly asserting ATN", mr->bus_status0);
+ dlog(ms, "bus0 was %.2x explicitly asserting ATN", mr->bus_status0);
out_8(&mr->bus_status0, BS0_ATN); /* explicit ATN */
mesh_flush_io(mr);
udelay(1);
--
Jean Delvare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|