From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, y00878127 <yangxiangkai@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 2454/2454] drivers/coda/coda.c:264: warning: Function parameter or member 's_smmu_id' not described in 'is_cc_vmid'
Date: Fri, 4 Jul 2025 06:26:48 +0800 [thread overview]
Message-ID: <202507040646.2QNfCtsv-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: 9b85bcf0e6357841885264f42859bec05c9073f4
commit: c5161d7e11a7e30755b2ec55aaebfd500193cbbc [2454/2454] virtCCA supports SR-IOV in CoDA scenarios.
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20250704/202507040646.2QNfCtsv-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250704/202507040646.2QNfCtsv-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/202507040646.2QNfCtsv-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/coda/coda.c:264: warning: Function parameter or member 's_smmu_id' not described in 'is_cc_vmid'
>> drivers/coda/coda.c:660: warning: Function parameter or member 'pci_dev' not described in 'virtcca_create_ste_entry'
>> drivers/coda/coda.c:660: warning: Excess function parameter 'smmu' description in 'virtcca_create_ste_entry'
>> drivers/coda/coda.c:660: warning: Excess function parameter 'master' description in 'virtcca_create_ste_entry'
>> drivers/coda/coda.c:660: warning: Excess function parameter 'sid' description in 'virtcca_create_ste_entry'
--
>> drivers/iommu/arm/arm-smmu-v3/arm-s-smmu-v3.c:56: warning: Function parameter or member 's_smmu_id' not described in 'virtcca_smmu_cmdq_need_forward'
vim +264 drivers/coda/coda.c
ad540a13eb8292 yangxiangkai 2024-09-20 254
ad540a13eb8292 yangxiangkai 2024-09-20 255 /**
c5161d7e11a7e3 yxk 2025-05-07 256 * is_cc_vmid - Whether the VM is confidential VM
c5161d7e11a7e3 yxk 2025-05-07 257 * @vmid: VM id
ad540a13eb8292 yangxiangkai 2024-09-20 258 *
ad540a13eb8292 yangxiangkai 2024-09-20 259 * Returns:
c5161d7e11a7e3 yxk 2025-05-07 260 * %true if the VM is confidential
c5161d7e11a7e3 yxk 2025-05-07 261 * %false if the VM is not confidential
ad540a13eb8292 yangxiangkai 2024-09-20 262 */
c5161d7e11a7e3 yxk 2025-05-07 263 bool is_cc_vmid(u32 vmid, u64 s_smmu_id)
ad540a13eb8292 yangxiangkai 2024-09-20 @264 {
ad540a13eb8292 yangxiangkai 2024-09-20 265 int bkt;
c5161d7e11a7e3 yxk 2025-05-07 266 struct coda_dev_hash_node *obj;
c5161d7e11a7e3 yxk 2025-05-07 267 bool secure = false;
ad540a13eb8292 yangxiangkai 2024-09-20 268
c5161d7e11a7e3 yxk 2025-05-07 269 spin_lock(&coda_dev_lock);
c5161d7e11a7e3 yxk 2025-05-07 270 hash_for_each(g_coda_dev_htable, bkt, obj, node) {
c5161d7e11a7e3 yxk 2025-05-07 271 if (vmid > 0 && obj->vmid == vmid && obj->s_smmu_id == s_smmu_id) {
c5161d7e11a7e3 yxk 2025-05-07 272 secure = obj->secure;
c5161d7e11a7e3 yxk 2025-05-07 273 spin_unlock(&coda_dev_lock);
c5161d7e11a7e3 yxk 2025-05-07 274 return secure;
c5161d7e11a7e3 yxk 2025-05-07 275 }
ad540a13eb8292 yangxiangkai 2024-09-20 276 }
ad540a13eb8292 yangxiangkai 2024-09-20 277
c5161d7e11a7e3 yxk 2025-05-07 278 spin_unlock(&coda_dev_lock);
c5161d7e11a7e3 yxk 2025-05-07 279 return secure;
ad540a13eb8292 yangxiangkai 2024-09-20 280 }
ad540a13eb8292 yangxiangkai 2024-09-20 281 EXPORT_SYMBOL_GPL(is_cc_vmid);
ad540a13eb8292 yangxiangkai 2024-09-20 282
:::::: The code at line 264 was first introduced by commit
:::::: ad540a13eb8292fc92651b3bf281088a502a85f9 virtcca feature: fix msi iova map
:::::: TO: yangxiangkai <yangxiangkai@huawei.com>
:::::: CC: yangxiangkai <yangxiangkai@huawei.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-03 22:27 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=202507040646.2QNfCtsv-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yangxiangkai@huawei.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 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.