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: Joe Perches <joe@perches.com>
Date: 2021-07-28 16:08:14
Also in: lkml

On Wed, 2021-07-28 at 08:55 -0700, Yury Norov wrote:
On Wed, Jul 28, 2021 at 08:13:32AM -0700, Joe Perches wrote:
quoted
On Wed, 2021-07-28 at 08:00 -0700, Yury Norov wrote:
quoted
Ping again.

The rebased series together with other bitmap patches can be found
here:

https://github.com/norov/linux/tree/bitmap-20210716
[]
quoted
quoted
 .../bitops => include/linux}/find.h           | 149 +++++++++++++++++-
A file named find.h in a directory named bitops seems relatively sensible,
but a bitops specific file named find.h in include/linux does not.
 

I'm OK with any name, it's not supposed to be included directly. What
do you think about bitmap_find.h, or can you suggest a better name?
Dunno.

But I'm a bit curious about the duplicate function naming (conflicts?)
with functions in include/linux/bitmap.h


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