1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/spinlocks.txt b/Documentation/spinlocks.txt
index 9dbe885ecd8d..97eaf5727178 100644
--- a/Documentation/spinlocks.txt
+++ b/Documentation/spinlocks.txt
@@ -137,7 +137,7 @@ don't block on each other (and thus there is no dead-lock wrt interrupts.
 But when you do the write-lock, you have to use the irq-safe version. 
 For an example of being clever with rw-locks, see the "waitqueue_lock" 
-handling in kernel/sched.c - nothing ever _changes_ a wait-queue from
+handling in kernel/sched/core.c - nothing ever _changes_ a wait-queue from
 within an interrupt, they only read the queue in order to know whom to
 wake up. So read-locks are safe (which is good: they are very common
 indeed), while write-locks need to protect themselves against interrupts.

diff --git a/Documentation/spinlocks.txt b/Documentation/spinlocks.txt index 9dbe885ecd8d..97eaf5727178 100644 --- a/Documentation/spinlocks.txt +++ b/Documentation/spinlocks.txt
@@ -137,7 +137,7 @@ don't block on each other (and thus there is no dead-lock wrt interrupts.
137	But when you do the write-lock, you have to use the irq-safe version.	137	But when you do the write-lock, you have to use the irq-safe version.
138		138
139	For an example of being clever with rw-locks, see the "waitqueue_lock"	139	For an example of being clever with rw-locks, see the "waitqueue_lock"
140	handling in kernel/sched.c - nothing ever _changes_ a wait-queue from	140	handling in kernel/sched/core.c - nothing ever _changes_ a wait-queue from
141	within an interrupt, they only read the queue in order to know whom to	141	within an interrupt, they only read the queue in order to know whom to
142	wake up. So read-locks are safe (which is good: they are very common	142	wake up. So read-locks are safe (which is good: they are very common
143	indeed), while write-locks need to protect themselves against interrupts.	143	indeed), while write-locks need to protect themselves against interrupts.