[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240903172214.520086-1-alparkerdf@gmail.com>
Date: Tue, 3 Sep 2024 13:22:14 -0400
From: alparkerdf@...il.com
To: axboe@...nel.dk,
linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Alvaro Parker <alparkerdf@...il.com>
Subject: [PATCH] block: fix comment to use set_current_state
From: Alvaro Parker <alparkerdf@...il.com>
The explanatory comment used `set_task_state` instead of
`set_current_state` which is the function actually used in the code.
Signed-off-by: Alvaro Parker <alparkerdf@...il.com>
---
block/blk-rq-qos.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/blk-rq-qos.c b/block/blk-rq-qos.c
index dd7310c94713..2cfb297d9a62 100644
--- a/block/blk-rq-qos.c
+++ b/block/blk-rq-qos.c
@@ -263,7 +263,7 @@ void rq_qos_wait(struct rq_wait *rqw, void *private_data,
has_sleeper = !prepare_to_wait_exclusive(&rqw->wait, &data.wq,
TASK_UNINTERRUPTIBLE);
do {
- /* The memory barrier in set_task_state saves us here. */
+ /* The memory barrier in set_current_state saves us here. */
if (data.got_token)
break;
if (!has_sleeper && acquire_inflight_cb(rqw, private_data)) {
--
2.46.0
Powered by blists - more mailing lists