From: Robin Murphy <robin.murphy@arm.com>
To: kernel test robot <lkp@intel.com>,
benve@cisco.com, neescoba@cisco.com, jgg@ziepe.ca
Cc: linux-rdma@vger.kernel.org, iommu@lists.linux-foundation.org,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/usnic: Refactor usnic_uiom_alloc_pd()
Date: Wed, 6 Apr 2022 22:39:47 +0100 [thread overview]
Message-ID: <87075d61-c51c-8d94-9263-17aa40f7d70e@arm.com> (raw)
In-Reply-To: <202204070316.vOzwORw5-lkp@intel.com>
On 2022-04-06 20:54, kernel test robot wrote:
> Hi Robin,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on rdma/for-next]
> [also build test ERROR on v5.18-rc1 next-20220406]
> [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]
Oops, I failed to notice that this does actually depend on the other
patch I sent cleaning up iommu_present()[1] - I should have sent them
together as a series, sorry about that.
Thanks,
Robin.
[1]
https://lore.kernel.org/linux-iommu/f707b4248e1d33b6d2c7f1d7c94febb802cf9890.1649161199.git.robin.murphy@arm.com/
>
> url: https://github.com/intel-lab-lkp/linux/commits/Robin-Murphy/RDMA-usnic-Refactor-usnic_uiom_alloc_pd/20220406-133657
> base: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
> config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220407/202204070316.vOzwORw5-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
> reproduce (this is a W=1 build):
> # https://github.com/intel-lab-lkp/linux/commit/0aa6215010a083081b26ccb23d0aa2b4089bbbfd
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Robin-Murphy/RDMA-usnic-Refactor-usnic_uiom_alloc_pd/20220406-133657
> git checkout 0aa6215010a083081b26ccb23d0aa2b4089bbbfd
> # save the config file to linux build tree
> mkdir build_dir
> make W=1 O=build_dir ARCH=i386 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 >>):
>
> drivers/infiniband/hw/usnic/usnic_uiom.c: In function 'usnic_uiom_init':
>>> drivers/infiniband/hw/usnic/usnic_uiom.c:561:29: error: 'pci_bus_type' undeclared (first use in this function); did you mean 'bus_type'?
> 561 | if (!iommu_present(&pci_bus_type)) {
> | ^~~~~~~~~~~~
> | bus_type
> drivers/infiniband/hw/usnic/usnic_uiom.c:561:29: note: each undeclared identifier is reported only once for each function it appears in
>
>
> vim +561 drivers/infiniband/hw/usnic/usnic_uiom.c
>
> e3cf00d0a87f02 Upinder Malhi 2013-09-10 558
> e3cf00d0a87f02 Upinder Malhi 2013-09-10 559 int usnic_uiom_init(char *drv_name)
> e3cf00d0a87f02 Upinder Malhi 2013-09-10 560 {
> e3cf00d0a87f02 Upinder Malhi 2013-09-10 @561 if (!iommu_present(&pci_bus_type)) {
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2022-04-06 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 14:35 [PATCH] RDMA/usnic: Refactor usnic_uiom_alloc_pd() Robin Murphy
2022-04-06 19:54 ` kernel test robot
2022-04-06 21:39 ` Robin Murphy [this message]
2022-04-06 21:53 ` Jason Gunthorpe
2022-04-08 17:23 ` Jason Gunthorpe via iommu
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=87075d61-c51c-8d94-9263-17aa40f7d70e@arm.com \
--to=robin.murphy@arm.com \
--cc=benve@cisco.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jgg@ziepe.ca \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lkp@intel.com \
--cc=neescoba@cisco.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