From: kernel test robot <lkp@intel.com>
To: "Nam Cao" <namcao@linutronix.de>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: <llvm@lists.linux.dev>, <oe-kbuild-all@lists.linux.dev>,
Nam Cao <namcao@linutronix.de>, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] PCI: iproc: Remove description of 'msi_domain' in struct iproc_msi
Date: Wed, 9 Jul 2025 09:17:07 +0800 [thread overview]
Message-ID: <aG3DE+J2sa6+12Mu@rli9-mobl> (raw)
In-Reply-To: <20250708053825.1803409-1-namcao@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
Hi Nam,
kernel test robot noticed the following build warnings:
[auto build test WARNING on pci/next]
[also build test WARNING on pci/for-linus linus/master v6.16-rc5 next-20250708]
[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/Nam-Cao/PCI-iproc-Remove-description-of-msi_domain-in-struct-iproc_msi/20250708-133907
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20250708053825.1803409-1-namcao%40linutronix.de
patch subject: [PATCH] PCI: iproc: Remove description of 'msi_domain' in struct iproc_msi
:::::: branch date: 11 hours ago
:::::: commit date: 11 hours ago
config: arm-randconfig-001-20250708 (attached as .config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 01c97b4953e87ae455bd4c41e3de3f0f0f29c61c)
reproduce (this is a W=1 build): (attached as 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/202507090000.aEkXHYpK-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/pci/controller/pcie-iproc-msi.c:108 struct member 'msi_domain' not described in 'iproc_msi'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38104 bytes --]
[-- Attachment #3: reproduce --]
[-- Type: text/plain, Size: 911 bytes --]
reproduce (this is a W=1 build):
git clone https://github.com/intel/lkp-tests.git ~/lkp-tests
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# clang-21 might not be officially released. Try a lower version if installation fails.
git remote add pci https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git
git fetch pci next
git checkout pci/next
b4 shazam https://lore.kernel.org/r/20250708053825.1803409-1-namcao@linutronix.de
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang-21 ~/lkp-tests/kbuild/make.cross W=1 O=build_dir ARCH=arm olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang-21 ~/lkp-tests/kbuild/make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/pci/controller/
prev parent reply other threads:[~2025-07-09 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 5:38 [PATCH] PCI: iproc: Remove description of 'msi_domain' in struct iproc_msi Nam Cao
2025-07-08 16:06 ` Bjorn Helgaas
2025-07-09 1:17 ` kernel test robot [this message]
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=aG3DE+J2sa6+12Mu@rli9-mobl \
--to=lkp@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=helgaas@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=namcao@linutronix.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=tglx@linutronix.de \
/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