From: kernel test robot <lkp@intel.com>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Joerg Roedel <jroedel@suse.de>, Jason Gunthorpe <jgg@nvidia.com>
Subject: drivers/iommu/amd/iommu.c:1269 domain_flush_complete() warn: inconsistent indenting
Date: Wed, 8 Jan 2025 01:50:55 +0800 [thread overview]
Message-ID: <202501080139.yHwH0ePx-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fbfd64d25c7af3b8695201ebc85efe90be28c5a3
commit: d16041124de1dea4389b5e6b330657f34f8c0492 iommu/amd: xarray to track protection_domain->iommu list
date: 10 weeks ago
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20250108/202501080139.yHwH0ePx-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
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/202501080139.yHwH0ePx-lkp@intel.com/
New smatch warnings:
drivers/iommu/amd/iommu.c:1269 domain_flush_complete() warn: inconsistent indenting
Old smatch warnings:
drivers/iommu/amd/iommu.c:1269 domain_flush_complete() warn: iterator 'i' not incremented
drivers/iommu/amd/iommu.c:1462 domain_flush_pages_v1() warn: iterator 'i' not incremented
drivers/iommu/amd/iommu.c:1996 init_gcr3_table() warn: missing error code? 'ret'
vim +1269 drivers/iommu/amd/iommu.c
1257
1258 static void domain_flush_complete(struct protection_domain *domain)
1259 {
1260 struct pdom_iommu_info *pdom_iommu_info;
1261 unsigned long i;
1262
1263 lockdep_assert_held(&domain->lock);
1264
1265 /*
1266 * Devices of this domain are behind this IOMMU
1267 * We need to wait for completion of all commands.
1268 */
> 1269 xa_for_each(&domain->iommu_array, i, pdom_iommu_info)
1270 iommu_completion_wait(pdom_iommu_info->iommu);
1271 }
1272
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-07 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202501080139.yHwH0ePx-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@nvidia.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vasant.hegde@amd.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
all inboxes | Powered by JetHome®