Hi, On 3/17/20 11:30 PM, Sasha Levin wrote:
Hi [This is an automated email] This commit has been processed because it contains a -stable tag. The stable tag indicates that it's relevant for the following trees: all The bot has tested the following trees: v5.5.9, v5.4.25, v4.19.109, v4.14.173, v4.9.216, v4.4.216. v5.5.9: Build OK! v5.4.25: Build OK! v4.19.109: Failed to apply! Possible dependencies: 0cc5359d8fd4 ("x86/cpu: Update init data for new Airmont CPU model") bba10c5cab4d ("x86/cpu: Use constant definitions for CPU models") v4.14.173: Failed to apply! Possible dependencies: 0cc5359d8fd4 ("x86/cpu: Update init data for new Airmont CPU model") 397d3ad18dc4 ("x86/tsc: Convert to use x86_match_cpu() and INTEL_CPU_FAM6()") bba10c5cab4d ("x86/cpu: Use constant definitions for CPU models") v4.9.216: Failed to apply! Possible dependencies: 0cc5359d8fd4 ("x86/cpu: Update init data for new Airmont CPU model") 397d3ad18dc4 ("x86/tsc: Convert to use x86_match_cpu() and INTEL_CPU_FAM6()") bba10c5cab4d ("x86/cpu: Use constant definitions for CPU models") v4.4.216: Failed to apply! Possible dependencies: 05680e7fa8a4 ("x86/tsc_msr: Correct Silvermont reference clock values") 0cc5359d8fd4 ("x86/cpu: Update init data for new Airmont CPU model") 397d3ad18dc4 ("x86/tsc: Convert to use x86_match_cpu() and INTEL_CPU_FAM6()") 6fcb41cdaee5 ("x86/tsc_msr: Add Airmont reference clock values") 9e0cae9f6227 ("x86/tsc_msr: Update comments, expand definitions") ba8268330dc1 ("x86/tsc_msr: Identify Intel-specific code") bba10c5cab4d ("x86/cpu: Use constant definitions for CPU models") NOTE: The patch will not be queued to stable trees until it is upstream. How should we proceed with this patch?
Just adding it to 5.4 / 5.5 is fine. It is not really a high prio fix. Regards, Hans