From: kernel test robot <lkp@intel.com>
To: Zhiping Zhang <zhipingz@meta.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>
Subject: drivers/infiniband/hw/mlx5/mr.c:913:20: error: no member named 'tph_req_type' in 'struct pci_dev'
Date: Wed, 13 May 2026 01:14:26 +0200 [thread overview]
Message-ID: <202605130114.zFnPmvo1-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Zhiping-Zhang/vfio-add-dma-buf-get_tph-callback-and-DMA_BUF_TPH-feature/20260505-063643
head: b58a906ae381ef91f4e88afd4862bee58a0c7bf2
commit: b58a906ae381ef91f4e88afd4862bee58a0c7bf2 RDMA/mlx5: get tph for p2p access when registering dma-buf mr
date: 8 days ago
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260513/202605130114.zFnPmvo1-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260513/202605130114.zFnPmvo1-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/202605130114.zFnPmvo1-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/infiniband/hw/mlx5/mr.c:913:20: error: no member named 'tph_req_type' in 'struct pci_dev'
913 | st_width = (pdev->tph_req_type == PCI_TPH_REQ_EXT_TPH) ? 16 : 8;
| ~~~~ ^
1 error generated.
vim +913 drivers/infiniband/hw/mlx5/mr.c
903
904 static void get_tph_mr_dmabuf(struct mlx5_ib_dev *dev, int fd, u16 *st_index,
905 u8 *ph)
906 {
907 struct pci_dev *pdev = dev->mdev->pdev;
908 struct dma_buf *dmabuf;
909 u16 steering_tag;
910 u8 st_width;
911 int ret;
912
> 913 st_width = (pdev->tph_req_type == PCI_TPH_REQ_EXT_TPH) ? 16 : 8;
914
915 dmabuf = dma_buf_get(fd);
916 if (IS_ERR(dmabuf))
917 return;
918
919 if (!dmabuf->ops->get_tph)
920 goto end_dbuf_put;
921
922 ret = dmabuf->ops->get_tph(dmabuf, &steering_tag, ph, st_width);
923 if (ret) {
924 mlx5_ib_dbg(dev, "get_tph failed (%d)\n", ret);
925 goto end_dbuf_put;
926 }
927
928 ret = mlx5_st_alloc_index_by_tag(dev->mdev, steering_tag, st_index);
929 if (ret) {
930 *ph = MLX5_IB_NO_PH;
931 mlx5_ib_dbg(dev, "st_alloc_index_by_tag failed (%d)\n", ret);
932 }
933
934 end_dbuf_put:
935 dma_buf_put(dmabuf);
936 }
937
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-12 23:14 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=202605130114.zFnPmvo1-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zhipingz@meta.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