[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250128164646.4009-9-yury.norov@gmail.com>
Date: Tue, 28 Jan 2025 11:46:37 -0500
From: Yury Norov <yury.norov@...il.com>
To: linux-kernel@...r.kernel.org,
	linux-crypto@...r.kernel.org,
	Steffen Klassert <steffen.klassert@...unet.com>,
	Daniel Jordan <daniel.m.jordan@...cle.com>
Cc: Yury Norov <yury.norov@...il.com>,
	Christoph Hellwig <hch@....de>,
	Rasmus Villemoes <linux@...musvillemoes.dk>,
	Herbert Xu <herbert@...dor.apana.org.au>
Subject: [PATCH v2 08/13] padata: switch padata_find_next() to using cpumask_next_wrap()
Calling cpumask_next_wrap_old() with starting CPU == -1 effectively means
the request to find next CPU, wrapping around if needed.
cpumask_next_wrap() is the proper replacement for that.
Acked-by: Herbert Xu <herbert@...dor.apana.org.au>
Acked-by: Daniel Jordan <daniel.m.jordan@...cle.com>
Signed-off-by: Yury Norov <yury.norov@...il.com>
---
 kernel/padata.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/padata.c b/kernel/padata.c
index 78e202fabf90..b3d4eacc4f5d 100644
--- a/kernel/padata.c
+++ b/kernel/padata.c
@@ -290,7 +290,7 @@ static struct padata_priv *padata_find_next(struct parallel_data *pd,
 	if (remove_object) {
 		list_del_init(&padata->list);
 		++pd->processed;
-		pd->cpu = cpumask_next_wrap_old(cpu, pd->cpumask.pcpu, -1, false);
+		pd->cpu = cpumask_next_wrap(cpu, pd->cpumask.pcpu);
 	}
 
 	spin_unlock(&reorder->lock);
-- 
2.43.0
Powered by blists - more mailing lists
 
