Thread (22 messages) 22 messages, 5 authors, 2021-07-28

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

From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: 2021-06-29 16:18:54
Also in: lkml

On Mon, Jun 28, 2021 at 06:48:20PM -0700, Yury Norov wrote:
On Sat, Jun 12, 2021 at 05:36:31AM -0700, Yury Norov wrote:
quoted
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: https://lore.kernel.org/lkml/YNirnaYw1GSxg1jK@yury-ThinkPad/T/ (local)
"This window" now equals for v5.15-rc1, hence we have a few weeks time anyway.

-- 
With Best Regards,
Andy Shevchenko

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help