From: kernel test robot <lkp@intel.com>
To: Sui Jingfeng <suijingfeng@loongson.cn>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
bhelgaas@google.com, linux-pci@vger.kernel.org,
loongson-kernel@lists.loongnix.cn, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] PCI/VGA: Make the vga_is_firmware_default() arch-independent
Date: Thu, 3 Aug 2023 20:25:45 +0800 [thread overview]
Message-ID: <202308032022.yiZngbbk-lkp@intel.com> (raw)
In-Reply-To: <20230803081758.968742-1-suijingfeng@loongson.cn>
Hi Sui,
kernel test robot noticed the following build errors:
[auto build test ERROR on pci/next]
[also build test ERROR on pci/for-linus linus/master v6.5-rc4 next-20230803]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Sui-Jingfeng/PCI-VGA-Make-the-vga_is_firmware_default-arch-independent/20230803-161838
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20230803081758.968742-1-suijingfeng%40loongson.cn
patch subject: [PATCH] PCI/VGA: Make the vga_is_firmware_default() arch-independent
config: arm64-randconfig-r026-20230731 (https://download.01.org/0day-ci/archive/20230803/202308032022.yiZngbbk-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20230803/202308032022.yiZngbbk-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/oe-kbuild-all/202308032022.yiZngbbk-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: screen_info
>>> referenced by vgaarb.c:86 (drivers/pci/vgaarb.c:86)
>>> drivers/pci/vgaarb.o:(vga_arb_firmware_fb_addr_tracker) in archive vmlinux.a
>>> referenced by vgaarb.c:86 (drivers/pci/vgaarb.c:86)
>>> drivers/pci/vgaarb.o:(vga_arb_firmware_fb_addr_tracker) in archive vmlinux.a
>>> referenced by vgaarb.c:88 (drivers/pci/vgaarb.c:88)
>>> drivers/pci/vgaarb.o:(vga_arb_firmware_fb_addr_tracker) in archive vmlinux.a
>>> referenced 3 more times
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-08-03 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 18:37 [PATCH] PCI/VGA: Fixup the firmware fb address om demanding time Sui Jingfeng
2023-08-01 22:51 ` kernel test robot
2023-08-02 2:27 ` kernel test robot
2023-08-02 3:40 ` kernel test robot
2023-08-02 6:24 ` suijingfeng
2023-08-03 8:17 ` [PATCH] PCI/VGA: Make the vga_is_firmware_default() arch-independent Sui Jingfeng
2023-08-03 12:25 ` kernel test robot [this message]
2023-08-04 3:11 ` suijingfeng
2023-08-04 16:38 ` Bjorn Helgaas
2023-08-10 20:49 ` 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=202308032022.yiZngbbk-lkp@intel.com \
--to=lkp@intel.com \
--cc=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=suijingfeng@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).