All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH RFC v3 8/8] lib/Kconfig.debug: introduce CONFIG_NO_AUTO_INLINE
Date: Fri, 2 May 2025 19:20:03 +0800	[thread overview]
Message-ID: <202505021916.FrmMx0sS-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "only suspicious fbc files changed"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250429-noautoinline-v3-8-4c49f28ea5b5@uniontech.com>
References: <20250429-noautoinline-v3-8-4c49f28ea5b5@uniontech.com>
TO: Chen Linxuan via B4 Relay <devnull+chenlinxuan.uniontech.com@kernel.org>

Hi Chen,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on ca91b9500108d4cf083a635c2e11c884d5dd20ea]

url:    https://github.com/intel-lab-lkp/linux/commits/Chen-Linxuan-via-B4-Relay/nvme-add-__always_inline-for-nvme_pci_npages_prp/20250429-120709
base:   ca91b9500108d4cf083a635c2e11c884d5dd20ea
patch link:    https://lore.kernel.org/r/20250429-noautoinline-v3-8-4c49f28ea5b5%40uniontech.com
patch subject: [PATCH RFC v3 8/8] lib/Kconfig.debug: introduce CONFIG_NO_AUTO_INLINE
:::::: branch date: 3 days ago
:::::: commit date: 3 days ago
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20250502/202505021916.FrmMx0sS-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250502/202505021916.FrmMx0sS-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202505021916.FrmMx0sS-lkp@intel.com/

All error/warnings (new ones prefixed by >>, old ones prefixed by <<):

>> WARNING: modpost: vmlinux: section mismatch in reference: zap_early_initrd_mapping+0x4 (section: .text) -> initrd_pl2p_start (section: .init.data)
>> WARNING: modpost: vmlinux: section mismatch in reference: zap_early_initrd_mapping+0xa (section: .text) -> initrd_pl2p_end (section: .init.data)
WARNING: modpost: vmlinux: section mismatch in reference: set_high_memory+0xb (section: .text) -> memblock_end_of_DRAM (section: .init.text)
>> WARNING: modpost: vmlinux: section mismatch in reference: set_high_memory+0x3e (section: .text) -> arch_zone_lowest_possible_pfn (section: .init.data)
>> ERROR: modpost: "__udivdi3" [drivers/usb/dwc3/dwc3-octeon.ko] undefined!

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2025-05-02 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 11:20 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-02  0:43 [PATCH RFC v3 8/8] lib/Kconfig.debug: introduce CONFIG_NO_AUTO_INLINE kernel test robot
2025-05-01 23:50 kernel test robot
2025-04-29  4:06 [PATCH RFC v3 0/8] kernel-hacking: " Chen Linxuan
2025-04-29  4:06 ` [PATCH RFC v3 8/8] lib/Kconfig.debug: " Chen Linxuan
2025-04-29  4:06   ` Chen Linxuan via B4 Relay
2025-05-02  9:56   ` kernel test robot

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=202505021916.FrmMx0sS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.