23 Apr
2025
23 Apr
'25
7:37 a.m.
On Tue, Apr 22, 2025 at 8:41 PM Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
The commit looks harmless. But I don't see how it could fix any warning?
I mean, we replace two !list_empty() checks by a single one ... and the warning is about list_cut_position() ?
I have no idea, actually. Maybe the double !list_empty() confuses the compiler, making it think `sublist` can be referenced out of the scope?
That is odd, are you sure this isn't a compiler bug?
I think it is a compiler bug. If so, what should we do to fix the warning?