From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 3382/3382] drivers/crypto/hisilicon/migration/acc_vf_migration.c:1622:43: error: 'struct pci_dev' has no member named 'sriov'
Date: Sat, 6 Dec 2025 05:42:08 +0800 [thread overview]
Message-ID: <202512060558.eWAtEGfZ-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-5.10
head: 06a8b520851290347ca458d4335bebc607fe3b58
commit: f1fd3a9b0bfc6f7da507ee6f9a32398c962281a6 [3382/3382] vfio/migration: Modify the vf id acquisition method
config: arm64-randconfig-r122-20251205 (https://download.01.org/0day-ci/archive/20251206/202512060558.eWAtEGfZ-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251206/202512060558.eWAtEGfZ-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/202512060558.eWAtEGfZ-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
In file included from drivers/crypto/hisilicon/migration/acc_vf_migration.c:11:
include/linux/pci.h: In function 'pci_physfn':
include/linux/pci.h:546:14: error: 'struct pci_dev' has no member named 'physfn'; did you mean 'is_physfn'?
dev = dev->physfn;
^~~~~~
is_physfn
drivers/crypto/hisilicon/migration/acc_vf_migration.c: In function 'vf_qm_pci_init':
drivers/crypto/hisilicon/migration/acc_vf_migration.c:1535:8: error: implicit declaration of function 'pci_request_mem_regions'; did you mean 'pci_request_regions'? [-Werror=implicit-function-declaration]
ret = pci_request_mem_regions(pdev, vfqm->dev_name);
^~~~~~~~~~~~~~~~~~~~~~~
pci_request_regions
drivers/crypto/hisilicon/migration/acc_vf_migration.c:1571:2: error: implicit declaration of function 'pci_release_mem_regions'; did you mean 'pci_release_regions'? [-Werror=implicit-function-declaration]
pci_release_mem_regions(pdev);
^~~~~~~~~~~~~~~~~~~~~~~
pci_release_regions
drivers/crypto/hisilicon/migration/acc_vf_migration.c: In function 'hisi_acc_get_vf_id':
>> drivers/crypto/hisilicon/migration/acc_vf_migration.c:1622:43: error: 'struct pci_dev' has no member named 'sriov'
((pf->bus->number << 8) + pf->devfn + pf->sriov->offset)) /
^~
drivers/crypto/hisilicon/migration/acc_vf_migration.c:1623:11: error: 'struct pci_dev' has no member named 'sriov'
pf->sriov->stride;
^~
drivers/crypto/hisilicon/migration/acc_vf_migration.c: In function 'acc_vf_probe':
drivers/crypto/hisilicon/migration/acc_vf_migration.c:1633:17: error: 'struct pci_dev' has no member named 'physfn'; did you mean 'is_physfn'?
pf_dev = pdev->physfn;
^~~~~~
is_physfn
drivers/crypto/hisilicon/migration/acc_vf_migration.c: In function 'hisi_acc_get_vf_id':
>> drivers/crypto/hisilicon/migration/acc_vf_migration.c:1624:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
cc1: some warnings being treated as errors
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for PCI_IOV
Depends on [n]: PCI [=n]
Selected by [y]:
- CRYPTO_DEV_HISI_MIGRATION [=y] && CRYPTO [=y] && CRYPTO_HW [=y] && ARM64 [=y] && ACPI [=y]
vim +1622 drivers/crypto/hisilicon/migration/acc_vf_migration.c
1612
1613 static int hisi_acc_get_vf_id(struct pci_dev *dev)
1614 {
1615 struct pci_dev *pf;
1616
1617 if (!dev->is_virtfn)
1618 return -EINVAL;
1619
1620 pf = pci_physfn(dev);
1621 return (((dev->bus->number << 8) + dev->devfn) -
> 1622 ((pf->bus->number << 8) + pf->devfn + pf->sriov->offset)) /
1623 pf->sriov->stride;
> 1624 }
1625
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-05 21:42 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=202512060558.eWAtEGfZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.