Re: Build regressions/improvements in v6.5-rc1 (cpufreq/sparc*)

[Randy Dunlap]

Hi--

On 7/10/23 03:00, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v6.5-rc1[1] compared to v6.4[2].
> 
> Summarized:
>   - build errors: +3/-4
>   - build warnings: +36/-18
> 
> Note that there may be false regressions, as some logs are incomplete.
> Still, they're build errors/warnings.
> 
> Happy fixing! ;-)
> 
> Thanks to the linux-next team for providing the build service.
> 
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5/ (all 162 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/6995e2de6891c724bfeb2db33d7b87775f913ad1/ (160 out of 162 configs)
> 
> 
> *** WARNINGS ***
> 
> 36 warning regressions:

>   + modpost: WARNING: modpost: drivers/cpufreq/sparc-us2e-cpufreq: section mismatch in reference: cpufreq_us2e_driver+0x20 (section: .data) -> us2e_freq_cpu_init (section: .init.text):  => N/A
>   + modpost: WARNING: modpost: drivers/cpufreq/sparc-us3-cpufreq: section mismatch in reference: cpufreq_us3_driver+0x20 (section: .data) -> us3_freq_cpu_init (section: .init.text):  => N/A

The way that I read this is that these __init functions (us2e_freq_cpu_init and us3_freq_cpu_init)
should not be marked as __init since they can be called at any time by exercising the CPU hotplug
code path.

-- 
~Randy