Skip to content

Commit

Permalink
typo fixes
Browse files Browse the repository at this point in the history
Signed-off-by: Adrian Bunk <[email protected]>
  • Loading branch information
[email protected] authored and AdrianBunk committed Jun 26, 2006
1 parent f274afc commit 2e2d0dc
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion Documentation/DocBook/kernel-locking.tmpl
Original file line number Diff line number Diff line change
Expand Up @@ -1590,7 +1590,7 @@ the amount of locking which needs to be done.
<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
Expand Down
2 changes: 1 addition & 1 deletion Documentation/driver-model/overview.txt
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Traditional driver models implemented some sort of tree-like structure
(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
Expand Down

0 comments on commit 2e2d0dc

Please sign in to comment.