On Tue, Feb 17, 2026 at 11:25:13AM -0800, Song Liu wrote: > On Tue, Feb 17, 2026 at 8:17 AM Joe Lawrence <[email protected]> wrote: > > > [...] > > > 2.53.0 > > > > > > > > > > Maybe I'm starting to see things, but when running 'S 2' builds, I keep > > getting "vmlinux.o: changed function: override_release". It could be > > considered benign for quick development work, or confusing. Seems easy > > enough to stash and avoid. > > "-S 2" with a different set of patches is only needed in patch development, > but not used for official releases. Therefore, I agree this is not a real > issue. >
My use case was running a series of tests: (test 1) - full build with -T (test N) - short circuit with -S 2 -T ... and where it confused me was that I had created tests which were designed to fail, specifically one wanted to verify no changes found for the recountdiff change in this set. Without this patch, that test will succeed as the version glitch gets picked up as: vmlinux.o: changed function: override_release I could work around that in verification, but then I miss the *specific* failure report from klp-build. I could also run each individual test as full, but each build was taking ~6 minutes on my machine. -- Joe
