[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected. No action required from the submitter.
The upstream commit SHA1 provided is correct: 96a720db59ab330c8562b2437153faa45dac705f
WARNING: Author mismatch between patch and upstream commit: Backport author: kan.liang@linux.intel.com Commit author: Kan Liangkan.liang@linux.intel.com
Status in newer kernel trees: 6.14.y | Present (different SHA1: 389ee3afddf6) 6.12.y | Present (different SHA1: 8d19c4a3b811) 6.6.y | Present (different SHA1: aea923afeae4) 6.1.y | Present (different SHA1: 8a809a8bcb89) 5.15.y | Present (different SHA1: 95ee595e4dfd)
Note: The patch differs from the upstream commit: --- 1: 96a720db59ab3 ! 1: 0a7c40d042397 perf/x86/intel/uncore: Fix the scale of IIO free running counters on SNR @@ Metadata ## Commit message ## perf/x86/intel/uncore: Fix the scale of IIO free running counters on SNR
+ [ Upstream commit 96a720db59ab330c8562b2437153faa45dac705f ] + + (The existing patch in queue-5.10 was wrong. + queue-5.10/perf-x86-intel-uncore-fix-the-scale-of-iio-free-running-counters-on-snr.patch + It's supposed to change the array snr_uncore_iio_freerunning_events[] + rather than icx_uncore_iio_freerunning_events[]. Send the patch to + replace the wrong one. + With this fix the https://lore.kernel.org/stable/2025042139-protector-rickety-a72d@gregkh/ + can be applied then.) + There was a mistake in the SNR uncore spec. The counter increments for every 32 bytes of data sent from the IO agent to the SOC, not 4 bytes which was documented in the spec. ---
Results of testing on various branches:
| Branch | Patch Apply | Build Test | |---------------------------|-------------|------------| | stable/linux-5.10.y | Success | Success |