mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
	Evgeniy Dushistov <dushistov@mail.ru>,
	Ira Weiny <ira.weiny@intel.com>,
	linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org
Subject: Re: [kbuild-all] Re: [PATCH] fs/ufs: Replace kmap() with kmap_local_page()
Date: Mon, 9 May 2022 17:10:19 +0800	[thread overview]
Message-ID: <b46bf8e8-9901-1026-2abf-ae7af163c7ad@intel.com> (raw)
In-Reply-To: <4710227.GXAFRqVoOG@leap>



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


  reply	other threads:[~2022-05-09  9:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 20:07 Fabio M. De Francesco
2022-05-08 23:44 ` kernel test robot
2022-05-09  6:04   ` Fabio M. De Francesco
2022-05-09  0:25 ` kernel test robot
2022-05-09  6:14   ` Fabio M. De Francesco
2022-05-09  9:10     ` Chen, Rong A [this message]
2022-05-09 12:49   ` Philip Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b46bf8e8-9901-1026-2abf-ae7af163c7ad@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=dushistov@mail.ru \
    --cc=fmdefrancesco@gmail.com \
    --cc=ira.weiny@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®