[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200422040739.18601-2-dave@stgolabs.net>
Date: Tue, 21 Apr 2020 21:07:35 -0700
From: Davidlohr Bueso <dave@...olabs.net>
To: tglx@...utronix.de, pbonzini@...hat.com
Cc: bigeasy@...utronix.de, peterz@...radead.org, rostedt@...dmis.org,
torvalds@...ux-foundation.org, will@...nel.org,
joel@...lfernandes.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, dave@...olabs.net,
Davidlohr Bueso <dbueso@...e.de>
Subject: [PATCH 1/5] rcuwait: Fix stale wake call name in comment
The 'trywake' name was renamed to simply 'wake', update the comment.
Signed-off-by: Davidlohr Bueso <dbueso@...e.de>
---
kernel/exit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/exit.c b/kernel/exit.c
index 389a88cb3081..9f9015f3f6b0 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -236,7 +236,7 @@ void rcuwait_wake_up(struct rcuwait *w)
/*
* Order condition vs @task, such that everything prior to the load
* of @task is visible. This is the condition as to why the user called
- * rcuwait_trywake() in the first place. Pairs with set_current_state()
+ * rcuwait_wake() in the first place. Pairs with set_current_state()
* barrier (A) in rcuwait_wait_event().
*
* WAIT WAKE
--
2.16.4
Powered by blists - more mailing lists