On Wed, Jun 18, 2025 at 7:44 PM Danilo Krummrich [off-list ref] wrote:

Independent from that, won't this potentially leave us with a lot of warnings
from code that goes through other trees in the upcoming merge window? How do we
deal with that?

Yeah, good question.

Since they are Clippy ones, it should not be a big deal (e.g. we
already had a case of a lint Clippy lingering for a long time due to
timing of merge window etc. in the QR code).

In this case, I didn't see new ones in -next yet when I looked, so it
should be mostly fine I think. It is also why I asked Tamir to re-send
it at the beginning of the cycle, and then a v12 to include a few
newer parts that were missed that landed lately.

So, worst case, they get fixed during the -rcs.

But, yeah, a while ago I proposed to have -rc1 to -rc2 as "treewide
cleanups time" -- it would make this sort of things (that is not fully
automated, but close) easy.

Cheers,
Miguel