Correct spelling problems for Documentation/locking/ as reported by codespell. Signed-off-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx> Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx> Cc: Ingo Molnar <mingo@xxxxxxxxxx> Cc: Will Deacon <will@xxxxxxxxxx> Cc: Jonathan Corbet <corbet@xxxxxxx> Cc: linux-doc@xxxxxxxxxxxxxxx --- Documentation/locking/lockdep-design.rst | 4 ++-- Documentation/locking/locktorture.rst | 2 +- Documentation/locking/locktypes.rst | 2 +- Documentation/locking/preempt-locking.rst | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff -- a/Documentation/locking/lockdep-design.rst b/Documentation/locking/lockdep-design.rst --- a/Documentation/locking/lockdep-design.rst +++ b/Documentation/locking/lockdep-design.rst @@ -29,7 +29,7 @@ the validator will shoot a splat if inco 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 rep +--------------+-------------+--------------+ 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. diff -- a/Documentation/locking/locktorture.rst b/Documentation/locking/locktorture.rst --- a/Documentation/locking/locktorture.rst +++ b/Documentation/locking/locktorture.rst @@ -113,7 +113,7 @@ stutter without pausing. shuffle_interval - The number of seconds to keep the test threads affinitied + The number of seconds to keep the test threads affined to a particular subset of the CPUs, defaults to 3 seconds. Used in conjunction with test_no_idle_hz. diff -- a/Documentation/locking/locktypes.rst b/Documentation/locking/locktypes.rst --- a/Documentation/locking/locktypes.rst +++ b/Documentation/locking/locktypes.rst @@ -500,7 +500,7 @@ caveats also apply to bit spinlocks. Some bit spinlocks are replaced with regular spinlock_t for PREEMPT_RT using conditional (#ifdef'ed) code changes at the usage site. In contrast, usage-site changes are not needed for the spinlock_t substitution. -Instead, conditionals in header files and the core locking implemementation +Instead, conditionals in header files and the core locking implementation enable the compiler to do the substitution transparently. diff -- a/Documentation/locking/preempt-locking.rst b/Documentation/locking/preempt-locking.rst --- a/Documentation/locking/preempt-locking.rst +++ b/Documentation/locking/preempt-locking.rst @@ -114,7 +114,7 @@ critical variables. Another example:: int buf[NR_CPUS]; set_cpu_val(buf); - if (buf[smp_processor_id()] == -1) printf(KERN_INFO "wee!\n"); + if (buf[smp_processor_id()] == -1) printf(KERN_INFO "whee!\n"); spin_lock(&buf_lock); /* ... */
