Andy Shevchenko wrote on Wed, Aug 13, 2025 at 04:52:39PM +0300: > > I actually test with W=1 too, but somehow this warning doesn't show up > > in my build, I'm not quite sure why :/ > > (even if I try clang like the test robot... But there's plenty of > > other warnings all around everywhere else, so I agree this is all way > > too manual) > > Depends on your config, last few releases I was specifically targetting x86 > defconfigs (32- and 64-bit) to be build with `make W=1`. There are a couple of > changes that are still pending, but otherwise it builds with GCC and clang. I meant it the other way around: the warning isn't showing up on master + these patches for my config. But now I double-checked, 'CC=clang make W=1' doesn't actually use clang, I should have tried 'make CC=clang W=1'... And, yeah, it just doesn't show up with gcc so I'll know it's better to check both compilers... Paul E. McKenney wrote on Wed, Aug 13, 2025 at 04:04:19PM -0700: > > I hope this to happen sooner as it broke my builds too (I always do now `make W=1` > > and suggest all developers should follow). > > This build failure is showing up in my testing as well. > > In the service of preventing bisection issues, would it be possible to > fold the fix into the original patch? Andrew just picked v3 up, so there won't be any such problem, and -next will stop failing after today's update -- Dominique Martinet | Asmadeus
