From 2e2d0dcc1bd7ca7c26ea5e29efb7f34bbd564f1c Mon Sep 17 00:00:00 2001 From: "olecom@mail.ru" Date: Mon, 26 Jun 2006 19:05:40 +0200 Subject: typo fixes Signed-off-by: Adrian Bunk --- Documentation/DocBook/kernel-locking.tmpl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Documentation/DocBook') diff --git a/Documentation/DocBook/kernel-locking.tmpl b/Documentation/DocBook/kernel-locking.tmpl index 158ffe9bfad..644c3884fab 100644 --- a/Documentation/DocBook/kernel-locking.tmpl +++ b/Documentation/DocBook/kernel-locking.tmpl @@ -1590,7 +1590,7 @@ the amount of locking which needs to be done. 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 next 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 -- cgit v1.2.3-70-g09d2