From: Niklas Cassel <cassel@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-pci@vger.kernel.org,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>
Subject: Re: [pci:endpoint-test 16/18] drivers/pci/controller/dwc/pcie-dw-rockchip.c:316:3: error: field designator 'intx_capable' does not refer to any field in type 'const struct dw_pcie_ep_ops'
Date: Mon, 10 Mar 2025 19:22:33 +0100 [thread overview]
Message-ID: <Z88t6TEjFCHDznmb@ryzen> (raw)
In-Reply-To: <202503110151.vQXf5yof-lkp@intel.com>
Hello Krzysztof,
On Tue, Mar 11, 2025 at 02:02:12AM +0800, kernel test robot wrote:
> Hi Niklas,
>
> FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git endpoint-test
> head: d87a0e7ac55245a3f75ca5c646ffdf0cfa36e749
> commit: da8628c06a7f08cb3402d02040d7a6195949772c [16/18] PCI: dw-rockchip: Endpoint mode cannot raise INTx interrupts
> config: s390-randconfig-001-20250311 (https://download.01.org/0day-ci/archive/20250311/202503110151.vQXf5yof-lkp@intel.com/config)
> compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250311/202503110151.vQXf5yof-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/202503110151.vQXf5yof-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> drivers/pci/controller/dwc/pcie-dw-rockchip.c:316:3: error: field designator 'intx_capable' does not refer to any field in type 'const struct dw_pcie_ep_ops'
> .intx_capable = false,
> ^
> drivers/pci/controller/dwc/pcie-dw-rockchip.c:530:33: warning: shift count >= width of type [-Wshift-count-overflow]
> dma_set_mask_and_coherent(dev, DMA_BIT_MASK(64));
> ^~~~~~~~~~~~~~~~
> include/linux/dma-mapping.h:73:54: note: expanded from macro 'DMA_BIT_MASK'
> #define DMA_BIT_MASK(n) (((n) == 64) ? ~0ULL : ((1ULL<<(n))-1))
> ^ ~~~
> 1 warning and 1 error generated.
>
>
> vim +316 drivers/pci/controller/dwc/pcie-dw-rockchip.c
>
> 313
> 314 static const struct dw_pcie_ep_ops rockchip_pcie_ep_ops = {
> 315 .init = rockchip_pcie_ep_init,
> > 316 .intx_capable = false,
> 317 .raise_irq = rockchip_pcie_raise_irq,
> 318 .get_features = rockchip_pcie_get_features,
> 319 };
> 320
>
This is not how the patch that I sent out looked like.
See:
https://lore.kernel.org/all/20250310111016.859445-14-cassel@kernel.org/
My guess is that you modified it before applying
(without adding [kwilczynski: ]).
If you undo your modifications, it should compile :)
Kind regards,
Niklas
next prev parent reply other threads:[~2025-03-10 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 18:02 [pci:endpoint-test 16/18] drivers/pci/controller/dwc/pcie-dw-rockchip.c:316:3: error: field designator 'intx_capable' does not refer to any field in type 'const struct dw_pcie_ep_ops' kernel test robot
2025-03-10 18:22 ` Niklas Cassel [this message]
2025-03-10 18:26 ` Krzysztof Wilczyński
2025-03-10 18:49 ` Krzysztof Wilczyński
2025-03-11 10:11 ` Niklas Cassel
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=Z88t6TEjFCHDznmb@ryzen \
--to=cassel@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox