From: kernel test robot <lkp@intel.com>
To: Shradha Todi <shradha.t@samsung.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, manivannan.sadhasivam@linaro.org,
lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
bhelgaas@google.com, jingoohan1@gmail.com,
Jonathan.Cameron@huawei.com, fan.ni@samsung.com,
a.manzanares@samsung.com, pankaj.dubey@samsung.com,
quic_nitegupt@quicinc.com, quic_krichai@quicinc.com,
gost.dev@samsung.com, Shradha Todi <shradha.t@samsung.com>
Subject: Re: [PATCH v4 1/2] PCI: dwc: Add support for vendor specific capability search
Date: Fri, 6 Dec 2024 20:02:36 +0800 [thread overview]
Message-ID: <202412061940.WSlxZ8i1-lkp@intel.com> (raw)
In-Reply-To: <20241206074456.17401-2-shradha.t@samsung.com>
Hi Shradha,
kernel test robot noticed the following build warnings:
[auto build test WARNING on pci/next]
[also build test WARNING on pci/for-linus mani-mhi/mhi-next linus/master v6.13-rc1 next-20241205]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Shradha-Todi/PCI-dwc-Add-support-for-vendor-specific-capability-search/20241206-163620
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20241206074456.17401-2-shradha.t%40samsung.com
patch subject: [PATCH v4 1/2] PCI: dwc: Add support for vendor specific capability search
config: i386-buildonly-randconfig-006 (https://download.01.org/0day-ci/archive/20241206/202412061940.WSlxZ8i1-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241206/202412061940.WSlxZ8i1-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/202412061940.WSlxZ8i1-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/pci/controller/dwc/pcie-designware.c: In function 'dw_pcie_find_vsec_capability':
>> drivers/pci/controller/dwc/pcie-designware.c:285:16: warning: suggest parentheses around assignment used as truth value [-Wparentheses]
285 | while (vsec = dw_pcie_find_next_ext_capability(pci, vsec,
| ^~~~
vim +285 drivers/pci/controller/dwc/pcie-designware.c
279
280 u16 dw_pcie_find_vsec_capability(struct dw_pcie *pci, u8 vsec_cap)
281 {
282 u16 vsec = 0;
283 u32 header;
284
> 285 while (vsec = dw_pcie_find_next_ext_capability(pci, vsec,
286 PCI_EXT_CAP_ID_VNDR)) {
287 header = dw_pcie_readl_dbi(pci, vsec + PCI_VNDR_HEADER);
288 if (PCI_VNDR_HEADER_ID(header) == vsec_cap)
289 return vsec;
290 }
291
292 return 0;
293 }
294 EXPORT_SYMBOL_GPL(dw_pcie_find_vsec_capability);
295
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-12-06 12:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241206074226epcas5p116df75209c19f95223761ba56d179a39@epcas5p1.samsung.com>
2024-12-06 7:44 ` [PATCH v4 0/2] Add support for RAS DES feature in PCIe DW Shradha Todi
2024-12-06 7:44 ` [PATCH v4 1/2] PCI: dwc: Add support for vendor specific capability search Shradha Todi
2024-12-06 12:02 ` kernel test robot [this message]
2024-12-06 12:57 ` kernel test robot
2024-12-06 16:13 ` Bjorn Helgaas
2024-12-11 11:45 ` Shradha Todi
2024-12-11 14:43 ` Bjorn Helgaas
2025-01-15 15:27 ` Manivannan Sadhasivam
2025-01-15 16:12 ` Bjorn Helgaas
2025-01-15 16:29 ` Manivannan Sadhasivam
2025-01-15 16:38 ` Bjorn Helgaas
2025-01-15 17:03 ` Shradha Todi
2025-01-16 7:12 ` Shradha Todi
2025-01-16 14:25 ` 'Manivannan Sadhasivam'
2024-12-06 7:44 ` [PATCH v4 2/2] PCI: dwc: Add debugfs based RASDES support in DWC Shradha Todi
2024-12-09 22:29 ` Fan Ni
2024-12-11 11:08 ` Shradha Todi
2025-01-15 16:55 ` Manivannan Sadhasivam
2025-01-07 12:21 ` Shradha Todi
2025-01-15 16:53 ` Manivannan Sadhasivam
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=202412061940.WSlxZ8i1-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=bhelgaas@google.com \
--cc=fan.ni@samsung.com \
--cc=gost.dev@samsung.com \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pankaj.dubey@samsung.com \
--cc=quic_krichai@quicinc.com \
--cc=quic_nitegupt@quicinc.com \
--cc=robh@kernel.org \
--cc=shradha.t@samsung.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