From: Alvaro Parker <alparkerdf@gmail.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@gmail.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

On Tue, 03 Sep 2024 13:22:14 -0400, alparkerdf@gmail.com wrote:
> The explanatory comment used `set_task_state` instead of
> `set_current_state` which is the function actually used in the code.
> 
> 

Applied, thanks!

[1/1] block: fix comment to use set_current_state
      commit: 2be6190cd75cd2029ced5ccef057e15939f48c4a

Best regards,
-- 
Jens Axboe