diff options
| author | Ralf Baechle <ralf@linux-mips.org> | 1998-08-25 09:12:35 +0000 |
|---|---|---|
| committer | Ralf Baechle <ralf@linux-mips.org> | 1998-08-25 09:12:35 +0000 |
| commit | c7fc24dc4420057f103afe8fc64524ebc25c5d37 (patch) | |
| tree | 3682407a599b8f9f03fc096298134cafba1c9b2f /Documentation/spinlocks.txt | |
| parent | 1d793fade8b063fde3cf275bf1a5c2d381292cd9 (diff) | |
o Merge with Linux 2.1.116.
o New Newport console code.
o New G364 console code.
Diffstat (limited to 'Documentation/spinlocks.txt')
| -rw-r--r-- | Documentation/spinlocks.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/spinlocks.txt b/Documentation/spinlocks.txt index 53f9362f5..c6e24f82d 100644 --- a/Documentation/spinlocks.txt +++ b/Documentation/spinlocks.txt @@ -11,7 +11,7 @@ On Fri, 2 Jan 1998, Doug Ledford wrote: > these routines and go about making use of them? Do they only lock on a > per-processor basis or can they also lock say an interrupt routine from > mucking with a queue if the queue routine was manipulating it when the -> interrupt occured, or should I still use a cli(); based construct on that +> interrupt occurred, or should I still use a cli(); based construct on that > one? See <asm/spinlock.h>. The basic version is: |