Re: bluetooth regression fix likely to miss -rc5 (was: Re: [GIT PULL] bluetooth 2026-03-19)

On Sat, 21 Mar 2026 at 11:50, Luiz Augusto von Dentz
[off-list ref] wrote:

Anyway, since this escalated rather quickly I think next time I'll
just revert and work out the situation on bluetooth-next, rather than
trying to access with the reporter and risk  delaying a fix.

Yes, I think that lowers the risk - and stress - for these kinds of things.

Generally, I think that if there are regressions reports that come in
while we're still in the -rc series and the problem hasn't hit an
actual release yet, it's probably worth reverting simply to get time
to think about the issue more.

(Of course - some bugs are simply obvious once somebody has bisected
the issue, and don't need any more time to think about it more. "D'oh,
too much cut-and-paste, obvious fix is obvious" - just apply the fix.
But if it's a situation where it's not entirely clear why things are
going south, and a revert is simple and straightforward, I don't think
there's much real downside to just going "ok, I don't know what's
going on, let's revert and rethink this")

The *good* thing about early regression reports is that typically the
people who test rc kernels are also very responsive to "can you test
this change" kinds of patches. So there is usually then a good path
forward for trying alternate approaches.

              Linus