diff options
author | Bjorn Helgaas <bhelgaas@google.com> | 2023-08-15 00:28:22 +0300 |
---|---|---|
committer | Jonathan Corbet <corbet@lwn.net> | 2023-08-18 20:29:03 +0300 |
commit | d56b699d76d1b352f7a3d3a0a3e91c79b8612d94 (patch) | |
tree | 2a368f3e2e17f7a516bf39e055f79d8c79a74885 /Documentation/locking/lockdep-design.rst | |
parent | ebab9426cd73c45945b44344ca904b343f0ca070 (diff) | |
download | linux-d56b699d76d1b352f7a3d3a0a3e91c79b8612d94.tar.xz |
Documentation: Fix typos
Fix typos in Documentation.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Link: https://lore.kernel.org/r/20230814212822.193684-4-helgaas@kernel.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/locking/lockdep-design.rst')
-rw-r--r-- | Documentation/locking/lockdep-design.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/locking/lockdep-design.rst b/Documentation/locking/lockdep-design.rst index 82f36cab61bd..56b90eea2731 100644 --- a/Documentation/locking/lockdep-design.rst +++ b/Documentation/locking/lockdep-design.rst @@ -29,7 +29,7 @@ the validator will shoot a splat if incorrect. A lock-class's behavior is constructed by its instances collectively: when the first instance of a lock-class is used after bootup the class gets registered, then all (subsequent) instances will be mapped to the -class and hence their usages and dependecies will contribute to those of +class and hence their usages and dependencies will contribute to those of the class. A lock-class does not go away when a lock instance does, but it can be removed if the memory space of the lock class (static or dynamic) is reclaimed, this happens for example when a module is @@ -105,7 +105,7 @@ exact case is for the lock as of the reporting time. +--------------+-------------+--------------+ The character '-' suggests irq is disabled because if otherwise the -charactor '?' would have been shown instead. Similar deduction can be +character '?' would have been shown instead. Similar deduction can be applied for '+' too. Unused locks (e.g., mutexes) cannot be part of the cause of an error. |