* [PATCH v2] kernel: locking: delete repeated words in comments
@ 2020-12-21 4:40 Randy Dunlap
2020-12-23 15:03 ` Will Deacon
0 siblings, 1 reply; 2+ messages in thread
From: Randy Dunlap @ 2020-12-21 4:40 UTC (permalink / raw)
To: linux-kernel; +Cc: Randy Dunlap, Peter Zijlstra, Ingo Molnar, Will Deacon
Drop repeated words in kernel/locking/.
{it, no, the}
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Will Deacon <will@kernel.org>
---
v2: rebase, resend
kernel/locking/rtmutex.c | 4 ++--
kernel/locking/rwsem.c | 2 +-
kernel/locking/semaphore.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
--- linux-next-20201218.orig/kernel/locking/rtmutex.c
+++ linux-next-20201218/kernel/locking/rtmutex.c
@@ -1438,7 +1438,7 @@ rt_mutex_fasttrylock(struct rt_mutex *lo
}
/*
- * Performs the wakeup of the the top-waiter and re-enables preemption.
+ * Performs the wakeup of the top-waiter and re-enables preemption.
*/
void rt_mutex_postunlock(struct wake_q_head *wake_q)
{
@@ -1833,7 +1833,7 @@ struct task_struct *rt_mutex_next_owner(
* been started.
* @waiter: the pre-initialized rt_mutex_waiter
*
- * Wait for the the lock acquisition started on our behalf by
+ * Wait for the lock acquisition started on our behalf by
* rt_mutex_start_proxy_lock(). Upon failure, the caller must call
* rt_mutex_cleanup_proxy_lock().
*
--- linux-next-20201218.orig/kernel/locking/rwsem.c
+++ linux-next-20201218/kernel/locking/rwsem.c
@@ -1048,7 +1048,7 @@ rwsem_down_write_slowpath(struct rw_sema
/*
* If there were already threads queued before us and:
- * 1) there are no no active locks, wake the front
+ * 1) there are no active locks, wake the front
* queued process(es) as the handoff bit might be set.
* 2) there are no active writers and some readers, the lock
* must be read owned; so we try to wake any read lock
--- linux-next-20201218.orig/kernel/locking/semaphore.c
+++ linux-next-20201218/kernel/locking/semaphore.c
@@ -119,7 +119,7 @@ EXPORT_SYMBOL(down_killable);
* @sem: the semaphore to be acquired
*
* Try to acquire the semaphore atomically. Returns 0 if the semaphore has
- * been acquired successfully or 1 if it it cannot be acquired.
+ * been acquired successfully or 1 if it cannot be acquired.
*
* NOTE: This return value is inverted from both spin_trylock and
* mutex_trylock! Be careful about this when converting code.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH v2] kernel: locking: delete repeated words in comments
2020-12-21 4:40 [PATCH v2] kernel: locking: delete repeated words in comments Randy Dunlap
@ 2020-12-23 15:03 ` Will Deacon
0 siblings, 0 replies; 2+ messages in thread
From: Will Deacon @ 2020-12-23 15:03 UTC (permalink / raw)
To: Randy Dunlap; +Cc: linux-kernel, Peter Zijlstra, Ingo Molnar
On Sun, Dec 20, 2020 at 08:40:48PM -0800, Randy Dunlap wrote:
> Drop repeated words in kernel/locking/.
> {it, no, the}
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Will Deacon <will@kernel.org>
> ---
> v2: rebase, resend
>
> kernel/locking/rtmutex.c | 4 ++--
> kernel/locking/rwsem.c | 2 +-
> kernel/locking/semaphore.c | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
Acked-by: Will Deacon <will@kernel.org>
Will
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-12-23 15:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-21 4:40 [PATCH v2] kernel: locking: delete repeated words in comments Randy Dunlap
2020-12-23 15:03 ` Will Deacon
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.