All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v2 3/3] Register auxiliary device for PCIe enclosure management
Date: Thu, 03 Feb 2022 13:02:36 +0800	[thread overview]
Message-ID: <202202031257.yEkdbEE2-lkp@intel.com> (raw)
In-Reply-To: <88898bbc85c85dce3c355c5f0399b593da0d4d27.1643822289.git.stuart.w.hayes@gmail.com>

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

Hi Stuart,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on helgaas-pci/next]
[also build test ERROR on char-misc/char-misc-testing pavel-leds/for-next linus/master v5.17-rc2 next-20220202]
[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]

url:    https://github.com/0day-ci/linux/commits/Stuart-Hayes/Add-PCIe-enclosure-management-support/20220203-020040
base:   https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
config: x86_64-randconfig-a003-20220131 (https://download.01.org/0day-ci/archive/20220203/202202031257.yEkdbEE2-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/407e7eb11ce495697eb2ee66d77f20d69548be14
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Stuart-Hayes/Add-PCIe-enclosure-management-support/20220203-020040
        git checkout 407e7eb11ce495697eb2ee66d77f20d69548be14
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

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: drivers/nvme/host/pci.o: in function `register_pcie_em_auxdev':
>> include/linux/pcie_em.h:71: undefined reference to `auxiliary_device_init'
>> ld: include/linux/pcie_em.h:75: undefined reference to `__auxiliary_device_add'


vim +71 include/linux/pcie_em.h

eefb0f75026145 Stuart Hayes 2022-02-02  53  
eefb0f75026145 Stuart Hayes 2022-02-02  54  static inline struct auxiliary_device *register_pcie_em_auxdev(struct device *dev, int id)
eefb0f75026145 Stuart Hayes 2022-02-02  55  {
eefb0f75026145 Stuart Hayes 2022-02-02  56  	struct auxiliary_device *adev;
eefb0f75026145 Stuart Hayes 2022-02-02  57  	int ret;
eefb0f75026145 Stuart Hayes 2022-02-02  58  
eefb0f75026145 Stuart Hayes 2022-02-02  59  	if (!pci_has_enclosure_management(to_pci_dev(dev)))
eefb0f75026145 Stuart Hayes 2022-02-02  60  		return NULL;
eefb0f75026145 Stuart Hayes 2022-02-02  61  
eefb0f75026145 Stuart Hayes 2022-02-02  62  	adev = kzalloc(sizeof(*adev), GFP_KERNEL);
eefb0f75026145 Stuart Hayes 2022-02-02  63  	if (!adev)
eefb0f75026145 Stuart Hayes 2022-02-02  64  		goto em_reg_out_err;
eefb0f75026145 Stuart Hayes 2022-02-02  65  
eefb0f75026145 Stuart Hayes 2022-02-02  66  	adev->name = "pcie_em";
eefb0f75026145 Stuart Hayes 2022-02-02  67  	adev->dev.parent = dev;
eefb0f75026145 Stuart Hayes 2022-02-02  68  	adev->dev.release = release_pcie_em_aux_device;
eefb0f75026145 Stuart Hayes 2022-02-02  69  	adev->id = id;
eefb0f75026145 Stuart Hayes 2022-02-02  70  
eefb0f75026145 Stuart Hayes 2022-02-02 @71  	ret = auxiliary_device_init(adev);
eefb0f75026145 Stuart Hayes 2022-02-02  72  	if (ret < 0)
eefb0f75026145 Stuart Hayes 2022-02-02  73  		goto em_reg_out_free;
eefb0f75026145 Stuart Hayes 2022-02-02  74  
eefb0f75026145 Stuart Hayes 2022-02-02 @75  	ret = auxiliary_device_add(adev);
eefb0f75026145 Stuart Hayes 2022-02-02  76  	if (ret) {
eefb0f75026145 Stuart Hayes 2022-02-02  77  		auxiliary_device_uninit(adev);
eefb0f75026145 Stuart Hayes 2022-02-02  78  		goto em_reg_out_free;
eefb0f75026145 Stuart Hayes 2022-02-02  79  	}
eefb0f75026145 Stuart Hayes 2022-02-02  80  
eefb0f75026145 Stuart Hayes 2022-02-02  81  	return adev;
eefb0f75026145 Stuart Hayes 2022-02-02  82  em_reg_out_free:
eefb0f75026145 Stuart Hayes 2022-02-02  83  	kfree(adev);
eefb0f75026145 Stuart Hayes 2022-02-02  84  em_reg_out_err:
eefb0f75026145 Stuart Hayes 2022-02-02  85  	dev_warn(dev, "failed to register pcie_em device\n");
eefb0f75026145 Stuart Hayes 2022-02-02  86  	return NULL;
eefb0f75026145 Stuart Hayes 2022-02-02  87  }
eefb0f75026145 Stuart Hayes 2022-02-02  88  

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

  parent reply	other threads:[~2022-02-03  5:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 17:59 [RFC PATCH v2 0/3] Add PCIe enclosure management support Stuart Hayes
2022-02-02 17:59 ` [RFC PATCH v2 1/3] Add support for seven more indicators in enclosure driver Stuart Hayes
2022-02-02 23:55   ` Bjorn Helgaas
2022-02-02 17:59 ` [RFC PATCH v2 2/3] Add PCIe enclosure management auxiliary driver Stuart Hayes
2022-02-03  0:58   ` Bjorn Helgaas
2022-02-02 17:59 ` [RFC PATCH v2 3/3] Register auxiliary device for PCIe enclosure management Stuart Hayes
2022-02-03  2:39   ` kernel test robot
2022-02-03  2:39     ` kernel test robot
2022-02-03  5:02   ` kernel test robot [this message]
2022-02-03  5:44   ` kernel test robot
2022-02-10 11:52 ` [RFC PATCH v2 0/3] Add PCIe enclosure management support Mariusz Tkaczyk

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=202202031257.yEkdbEE2-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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.