From: kernel test robot <lkp@intel.com>
To: Hans Zhang <18255117159@163.com>, tglx@linutronix.de
Cc: oe-kbuild-all@lists.linux.dev, manivannan.sadhasivam@linaro.org,
kw@linux.com, kwilczynski@kernel.org, bhelgaas@google.com,
Frank.Li@nxp.com, cassel@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, Hans Zhang <18255117159@163.com>
Subject: Re: [v2] genirq/msi: Add the address and data that show MSI/MSIX
Date: Sun, 2 Mar 2025 09:12:04 +0800 [thread overview]
Message-ID: <202503020812.PKZf7JBa-lkp@intel.com> (raw)
In-Reply-To: <20250301123953.291675-1-18255117159@163.com>
Hi Hans,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 76544811c850a1f4c055aa182b513b7a843868ea]
url: https://github.com/intel-lab-lkp/linux/commits/Hans-Zhang/genirq-msi-Add-the-address-and-data-that-show-MSI-MSIX/20250301-204332
base: 76544811c850a1f4c055aa182b513b7a843868ea
patch link: https://lore.kernel.org/r/20250301123953.291675-1-18255117159%40163.com
patch subject: [v2] genirq/msi: Add the address and data that show MSI/MSIX
config: arm-randconfig-001-20250302 (https://download.01.org/0day-ci/archive/20250302/202503020812.PKZf7JBa-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250302/202503020812.PKZf7JBa-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/202503020812.PKZf7JBa-lkp@intel.com/
All warnings (new ones prefixed by >>):
kernel/irq/msi.c: In function 'msi_domain_debug_show':
kernel/irq/msi.c:770:9: error: implicit declaration of function 'seq_printf'; did you mean 'bstr_printf'? [-Wimplicit-function-declaration]
770 | seq_printf(m, "%*s%s:", ind, "", is_msix ? "msix" : "msi");
| ^~~~~~~~~~
| bstr_printf
kernel/irq/msi.c: At top level:
kernel/irq/msi.c:782:10: error: 'const struct irq_domain_ops' has no member named 'debug_show'
782 | .debug_show = msi_domain_debug_show,
| ^~~~~~~~~~
>> kernel/irq/msi.c:782:27: warning: excess elements in struct initializer
782 | .debug_show = msi_domain_debug_show,
| ^~~~~~~~~~~~~~~~~~~~~
kernel/irq/msi.c:782:27: note: (near initialization for 'msi_domain_ops')
vim +782 kernel/irq/msi.c
775
776 static const struct irq_domain_ops msi_domain_ops = {
777 .alloc = msi_domain_alloc,
778 .free = msi_domain_free,
779 .activate = msi_domain_activate,
780 .deactivate = msi_domain_deactivate,
781 .translate = msi_domain_translate,
> 782 .debug_show = msi_domain_debug_show,
783 };
784
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-02 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 12:39 [v2] genirq/msi: Add the address and data that show MSI/MSIX Hans Zhang
2025-03-02 1:12 ` kernel test robot [this message]
2025-03-02 1:12 ` kernel test robot
2025-03-02 9:01 ` Thomas Gleixner
2025-03-02 14:45 ` Hans Zhang
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=202503020812.PKZf7JBa-lkp@intel.com \
--to=lkp@intel.com \
--cc=18255117159@163.com \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=kw@linux.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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