Re: [PATCH 0/8] all: use find_next_*_bit() instead of find_first_*_bit() where possible

From: Yury Norov
Date: Mon Jun 28 2021 - 21:48:36 EST

On Sat, Jun 12, 2021 at 05:36:31AM -0700, Yury Norov wrote:
> find_first_*_bit() is simpler and faster than 'next' version [1], and they
> work identically if start == 0. But in many cases kernel code uses the
> 'next' version where 'first' can be used. This series addresses this issue.
> Patches 1-3 move find.h under include/linux as it simplifies development.
> Patches 4-8 switch the kernel and tools to find_first_*_bit() implementation
> where appropriate.

Guys, do we have any blocker for this series? If not, I'd like to have it
merged in this window.

And this too: