Hi ! Maybe this will be useful.
docs-kernlock_typo.spatch:
--- linux-source-2.6.16/Documentation/DocBook/kernel-locking.tmpl~ 2006-03-20 06:53:29.000000000 +0100
+++ linux-source-2.6.16/Documentation/DocBook/kernel-locking.tmpl 2006-06-09 06:56:58.038022250 +0200
@@ -1590,7 +1590,7 @@
<para>
Our final dilemma is this: when can we actually destroy the
removed element? Remember, a reader might be stepping through
- this element in the list right now: it we free this element and
+ this element in the list right now: if we free this element and
the <symbol>next</symbol> pointer changes, the reader will jump
off into garbage and crash. We need to wait until we know that
all the readers who were traversing the list when we deleted the
docs-drv-overview_typo.spatch:
--- linux-source-2.6.16/Documentation/driver-model/overview.txt~ 2006-03-20 06:53:29.000000000 +0100
+++ linux-source-2.6.16/Documentation/driver-model/overview.txt 2006-06-09 06:52:00.171406750 +0200
@@ -18,7 +18,7 @@
(sometimes just a list) for the devices they control. There wasn't any
uniformity across the different bus types.
-The current driver model provides a comon, uniform data model for describing
+The current driver model provides a common, uniform data model for describing
a bus and the devices that can appear under the bus. The unified bus
model includes a set of common attributes which all busses carry, and a set
of common callbacks, such as device discovery during bus probing, bus
-
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
