[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176764558097.1441586.5364156428350110916.b4-ty@kernel.org>
Date: Mon, 5 Jan 2026 22:58:30 +0000
From: Will Deacon <will@...nel.org>
To: Atish Patra <atish.patra@...ux.dev>,
Anup Patel <anup@...infault.org>,
Mark Rutland <mark.rutland@....com>,
Paul Walmsley <pjw@...nel.org>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Alexandre Ghiti <alex@...ti.fr>,
Ji Sheng Teoh <jisheng.teoh@...rfivetech.com>,
linux-riscv@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org,
"Yury Norov (NVIDIA)" <yury.norov@...il.com>
Cc: catalin.marinas@....com,
kernel-team@...roid.com,
Will Deacon <will@...nel.org>
Subject: Re: [PATCH] drivers: perf: use bitmap_empty() where appropriate
On Mon, 15 Dec 2025 20:20:03 -0500, Yury Norov (NVIDIA) wrote:
> bitmap_empty() is more verbose and efficient, as it stops traversing
> bitmaps as soon as the 1st set bit found.
>
> Switch perf code to using bitmap_empty() where appropriate, and
> correspondingly use boolean types.
>
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] drivers: perf: use bitmap_empty() where appropriate
https://git.kernel.org/will/c/0c7c64146f70
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists