Re: [PATCH 5.15.y] ring-buffer: Remove ring_buffer_read_prepare_sync()

[Sasha Levin]

> [PATCH 5.15.y] ring-buffer: Remove ring_buffer_read_prepare_sync()

I had to drop this one for 5.15. The upstream guard(raw_spinlock_irqsave)
conversion in ring_buffer_read_start() introduces a new
-Wdeclaration-after-statement warning on 5.15 (the guard variable ends up after
a statement), which the build flags as an
error there.

Could you respin a warning-free version for 5.15 (and 5.10, which has the same
problem)? E.g. hoisting the declaration or keeping the explicit
raw_spin_lock/unlock instead of guard() on these older trees.  6.6 and 6.1 are
already queued.

--
Thanks,
Sasha