Re: [kbuild-all] Re: [PATCH] fs/ufs: Replace kmap() with kmap_local_page()

[Chen, Rong A]

On 5/9/2022 2:14 PM, Fabio M. De Francesco wrote:
> On lunedì 9 maggio 2022 02:25:00 CEST kernel test robot wrote:
> > Hi "Fabio,

Hi Fabio,

Here is a note:

> > Note: the below error/warnings can be found in parent commit:
> > << WARNING: modpost: vmlinux.o(.text+0xa76d10): Section mismatch in
> reference from the function rtc_update_irq() to the variable .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.exit.text+0x9b48): Section mismatch in
> reference from the function rproc_exit_sysfs() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(__ex_table+0x141c): Section mismatch in
> reference from the variable .L0 to the variable .debug_str:.LASF1567
> > << WARNING: modpost: vmlinux.o(.text+0xa7839c): Section mismatch in
> reference from the function rtc_get_dev_attribute_groups() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2676): Section mismatch in
> reference from the function ir_raw_get_allowed_protocols() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2cb8): Section mismatch in
> reference from the function ir_raw_event_prepare() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2e16): Section mismatch in
> reference from the function ir_raw_event_free() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2e3a): Section mismatch in
> reference from the function ir_raw_event_unregister() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xb35172): Section mismatch in
> reference from the function btintel_enter_mfg() to the variable
> .init.text:.LBB19521
> > << WARNING: modpost: vmlinux.o(.text+0xa76d10): Section mismatch in
> reference from the function rtc_update_irq() to the variable .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.exit.text+0x9b48): Section mismatch in
> reference from the function rproc_exit_sysfs() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(__ex_table+0x141c): Section mismatch in
> reference from the variable .L0 to the variable .debug_str:.LASF1567
> > << WARNING: modpost: vmlinux.o(.text+0xa7839c): Section mismatch in
> reference from the function rtc_get_dev_attribute_groups() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2676): Section mismatch in
> reference from the function ir_raw_get_allowed_protocols() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2cb8): Section mismatch in
> reference from the function ir_raw_event_prepare() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2e16): Section mismatch in
> reference from the function ir_raw_event_free() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2e3a): Section mismatch in
> reference from the function ir_raw_event_unregister() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xb35172): Section mismatch in
> reference from the function btintel_enter_mfg() to the variable
> .init.text:.LBB19521
> > << WARNING: modpost: vmlinux.o(.text+0xa76d10): Section mismatch in
> reference from the function rtc_update_irq() to the variable .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.exit.text+0x9b48): Section mismatch in
> reference from the function rproc_exit_sysfs() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(__ex_table+0x141c): Section mismatch in
> reference from the variable .L0 to the variable .debug_str:.LASF1567
> > << WARNING: modpost: vmlinux.o(.text+0xa7839c): Section mismatch in
> reference from the function rtc_get_dev_attribute_groups() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2676): Section mismatch in
> reference from the function ir_raw_get_allowed_protocols() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2cb8): Section mismatch in
> reference from the function ir_raw_event_prepare() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2e16): Section mismatch in
> reference from the function ir_raw_event_free() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2e3a): Section mismatch in
> reference from the function ir_raw_event_unregister() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xb35172): Section mismatch in
> reference from the function btintel_enter_mfg() to the variable
> .init.text:.LBB19521
> > << WARNING: modpost: vmlinux.o(.text+0xa76d10): Section mismatch in
> reference from the function rtc_update_irq() to the variable .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.exit.text+0x9b48): Section mismatch in
> reference from the function rproc_exit_sysfs() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(__ex_table+0x141c): Section mismatch in
> reference from the variable .L0 to the variable .debug_str:.LASF1567
> > << WARNING: modpost: vmlinux.o(.text+0xa7839c): Section mismatch in
> reference from the function rtc_get_dev_attribute_groups() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2676): Section mismatch in
> reference from the function ir_raw_get_allowed_protocols() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2cb8): Section mismatch in
> reference from the function ir_raw_event_prepare() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2e16): Section mismatch in
> reference from the function ir_raw_event_free() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xae2e3a): Section mismatch in
> reference from the function ir_raw_event_unregister() to the variable
> .init.text:.L0
> > << WARNING: modpost: vmlinux.o(.text+0xb35172): Section mismatch in
> reference from the function btintel_enter_mfg() to the variable
> .init.text:.LBB19521
> > --
> > 0-DAY CI Kernel Test Service
> > https://01.org/lkp
> I cannot understand this report. All the functions listed here seem to have
> nothing to do with my patch. Can anyone explain how these errors are
> related to my changes?
>
> Thanks,
>
> Fabio


Please ignore this report, a lot of similar warnings can be found in 
parent commit.

Best Regards,
Rong Chen