From: kernel test robot <lkp@intel.com>
To: Huang Jiaqing <jiaqing.huang@intel.com>,
kvm@vger.kernel.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, joro@8bytes.org, will@kernel.org,
robin.murphy@arm.com, kevin.tian@intel.com,
baolu.lu@linux.intel.com, jacob.jun.pan@linux.intel.com,
yi.l.liu@intel.com, yi.y.sun@intel.com, jiaqing.huang@intel.com
Subject: Re: [PATCH] iommu/vt-d: Introduce a rb_tree for looking up device
Date: Wed, 23 Aug 2023 09:47:48 +0800 [thread overview]
Message-ID: <202308230922.9PKf5JkV-lkp@intel.com> (raw)
In-Reply-To: <20230821071659.123981-1-jiaqing.huang@intel.com>
Hi Huang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.5-rc7]
[also build test WARNING on linus/master]
[cannot apply to joro-iommu/next next-20230822]
[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/Huang-Jiaqing/iommu-vt-d-Introduce-a-rb_tree-for-looking-up-device/20230821-151945
base: v6.5-rc7
patch link: https://lore.kernel.org/r/20230821071659.123981-1-jiaqing.huang%40intel.com
patch subject: [PATCH] iommu/vt-d: Introduce a rb_tree for looking up device
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20230823/202308230922.9PKf5JkV-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230823/202308230922.9PKf5JkV-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/202308230922.9PKf5JkV-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/iommu/intel/iommu.c:239:28: warning: no previous prototype for 'device_rbtree_find' [-Wmissing-prototypes]
239 | struct device_domain_info *device_rbtree_find(struct intel_iommu *iommu, u8 bus, u8 devfn)
| ^~~~~~~~~~~~~~~~~~
vim +/device_rbtree_find +239 drivers/iommu/intel/iommu.c
237
238
> 239 struct device_domain_info *device_rbtree_find(struct intel_iommu *iommu, u8 bus, u8 devfn)
240 {
241 struct device_domain_info *data = NULL;
242 struct rb_node *node;
243
244 down_read(&iommu->iopf_device_sem);
245
246 node = iommu->iopf_device_rbtree.rb_node;
247 while (node) {
248 data = container_of(node, struct device_domain_info, node);
249 s16 result = RB_NODE_CMP(bus, devfn, data->bus, data->devfn);
250
251 if (result < 0)
252 node = node->rb_left;
253 else if (result > 0)
254 node = node->rb_right;
255 else
256 break;
257 }
258 up_read(&iommu->iopf_device_sem);
259
260 return node ? data : NULL;
261 }
262
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-08-23 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 7:16 [PATCH] iommu/vt-d: Introduce a rb_tree for looking up device Huang Jiaqing
2023-08-21 16:52 ` Jason Gunthorpe
2023-08-22 7:32 ` Baolu Lu
2023-08-23 1:47 ` kernel test robot [this message]
2023-08-23 10:19 ` kernel test robot
2023-09-25 8:12 ` Joerg Roedel
2023-09-26 8:25 ` Huang, Jiaqing
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=202308230922.9PKf5JkV-lkp@intel.com \
--to=lkp@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jiaqing.huang@intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@intel.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