public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Garrit Franke <garritfranke@gmail.com>,
	rjw@rjwysocki.net, lenb@kernel.org
Cc: kbuild-all@lists.01.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] acpi: apei-base: fix sparse warnings
Date: Sun, 21 Jun 2020 13:10:08 +0800	[thread overview]
Message-ID: <202006211308.qBTUEUXg%lkp@intel.com> (raw)
In-Reply-To: <20200610162939.GA105986@garrit-VirtualBox>

[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]

Hi Garrit,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on pm/linux-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use  as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Garrit-Franke/acpi-apei-base-fix-sparse-warnings/20200611-003136
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: x86_64-randconfig-a012-20200621 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce (this is a W=1 build):
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   ld: arch/x86/pci/mmconfig-shared.o: in function `pci_mmcfg_early_init':
>> arch/x86/pci/mmconfig-shared.c:671: undefined reference to `arch_apei_filter_addr'
>> ld: arch/x86/pci/mmconfig-shared.c:671: undefined reference to `arch_apei_filter_addr'
>> ld: arch/x86/pci/mmconfig-shared.c:671: undefined reference to `arch_apei_filter_addr'

vim +671 arch/x86/pci/mmconfig-shared.c

574a59414083df Jiang Liu  2012-06-22  661  
bb63b4219976d4 Yinghai Lu 2008-02-28  662  void __init pci_mmcfg_early_init(void)
05c58b8ac77639 Yinghai Lu 2008-02-15  663  {
574a59414083df Jiang Liu  2012-06-22  664  	if (pci_probe & PCI_PROBE_MMCONF) {
574a59414083df Jiang Liu  2012-06-22  665  		if (pci_mmcfg_check_hostbridge())
574a59414083df Jiang Liu  2012-06-22  666  			known_bridge = 1;
574a59414083df Jiang Liu  2012-06-22  667  		else
574a59414083df Jiang Liu  2012-06-22  668  			acpi_sfi_table_parse(ACPI_SIG_MCFG, pci_parse_mcfg);
bb63b4219976d4 Yinghai Lu 2008-02-28  669  		__pci_mmcfg_init(1);
d91525eb8ee6a6 Chen, Gong 2014-12-10  670  
d91525eb8ee6a6 Chen, Gong 2014-12-10 @671  		set_apei_filter();
05c58b8ac77639 Yinghai Lu 2008-02-15  672  	}
574a59414083df Jiang Liu  2012-06-22  673  }
05c58b8ac77639 Yinghai Lu 2008-02-15  674  

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 36618 bytes --]

      reply	other threads:[~2020-06-21  5:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 16:29 [PATCH] acpi: apei-base: fix sparse warnings Garrit Franke
2020-06-21  5:10 ` kernel test robot [this message]

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=202006211308.qBTUEUXg%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=garritfranke@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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