From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH hyperv-next v5 08/11] Drivers: hv: vmbus: Get the IRQ number from DeviceTree
Date: Thu, 13 Mar 2025 23:57:26 +0800 [thread overview]
Message-ID: <202503132345.uKNehsnm-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250307220304.247725-9-romank@linux.microsoft.com>
References: <20250307220304.247725-9-romank@linux.microsoft.com>
TO: Roman Kisel <romank@linux.microsoft.com>
TO: arnd@arndb.de
TO: bhelgaas@google.com
TO: bp@alien8.de
TO: catalin.marinas@arm.com
TO: conor+dt@kernel.org
TO: dave.hansen@linux.intel.com
TO: decui@microsoft.com
TO: haiyangz@microsoft.com
TO: hpa@zytor.com
TO: joey.gouly@arm.com
TO: krzk+dt@kernel.org
TO: kw@linux.com
TO: kys@microsoft.com
TO: lenb@kernel.org
TO: lpieralisi@kernel.org
TO: manivannan.sadhasivam@linaro.org
TO: mark.rutland@arm.com
TO: maz@kernel.org
TO: mingo@redhat.com
TO: oliver.upton@linux.dev
TO: rafael@kernel.org
TO: robh@kernel.org
TO: ssengar@linux.microsoft.com
TO: sudeep.holla@arm.com
TO: suzuki.poulose@arm.com
TO: tglx@linutronix.de
TO: wei.liu@kernel.org
TO: will@kernel.org
TO: yuzenghui@huawei.com
TO: devicetree@vger.kernel.org
Hi Roman,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 3a7f7785eae7cf012af128ca9e383c91e4955354]
url: https://github.com/intel-lab-lkp/linux/commits/Roman-Kisel/arm64-kvm-smccc-Introduce-and-use-API-for-detectting-hypervisor-presence/20250308-060639
base: 3a7f7785eae7cf012af128ca9e383c91e4955354
patch link: https://lore.kernel.org/r/20250307220304.247725-9-romank%40linux.microsoft.com
patch subject: [PATCH hyperv-next v5 08/11] Drivers: hv: vmbus: Get the IRQ number from DeviceTree
:::::: branch date: 6 days ago
:::::: commit date: 6 days ago
config: arm64-randconfig-r071-20250312 (https://download.01.org/0day-ci/archive/20250313/202503132345.uKNehsnm-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202503132345.uKNehsnm-lkp@intel.com/
smatch warnings:
drivers/hv/vmbus_drv.c:2355 vmbus_set_irq() warn: platform_get_irq() does not return zero
vim +2355 drivers/hv/vmbus_drv.c
f83705a51275ed2 Saurabh Sengar 2023-03-20 2347
2e494cbd89c51d1 Roman Kisel 2025-03-07 2348 static int __maybe_unused vmbus_set_irq(struct platform_device *pdev)
2e494cbd89c51d1 Roman Kisel 2025-03-07 2349 {
2e494cbd89c51d1 Roman Kisel 2025-03-07 2350 struct irq_data *data;
2e494cbd89c51d1 Roman Kisel 2025-03-07 2351 int irq;
2e494cbd89c51d1 Roman Kisel 2025-03-07 2352 irq_hw_number_t hwirq;
2e494cbd89c51d1 Roman Kisel 2025-03-07 2353
2e494cbd89c51d1 Roman Kisel 2025-03-07 2354 irq = platform_get_irq(pdev, 0);
2e494cbd89c51d1 Roman Kisel 2025-03-07 @2355 if (irq == 0) {
2e494cbd89c51d1 Roman Kisel 2025-03-07 2356 pr_err("VMBus interrupt mapping failure\n");
2e494cbd89c51d1 Roman Kisel 2025-03-07 2357 return -EINVAL;
2e494cbd89c51d1 Roman Kisel 2025-03-07 2358 }
2e494cbd89c51d1 Roman Kisel 2025-03-07 2359 if (irq < 0) {
2e494cbd89c51d1 Roman Kisel 2025-03-07 2360 pr_err("VMBus interrupt data can't be read from DeviceTree, error %d\n", irq);
2e494cbd89c51d1 Roman Kisel 2025-03-07 2361 return irq;
2e494cbd89c51d1 Roman Kisel 2025-03-07 2362 }
2e494cbd89c51d1 Roman Kisel 2025-03-07 2363
2e494cbd89c51d1 Roman Kisel 2025-03-07 2364 data = irq_get_irq_data(irq);
2e494cbd89c51d1 Roman Kisel 2025-03-07 2365 if (!data) {
2e494cbd89c51d1 Roman Kisel 2025-03-07 2366 pr_err("No interrupt data for VMBus virq %d\n", irq);
2e494cbd89c51d1 Roman Kisel 2025-03-07 2367 return -ENODEV;
2e494cbd89c51d1 Roman Kisel 2025-03-07 2368 }
2e494cbd89c51d1 Roman Kisel 2025-03-07 2369 hwirq = irqd_to_hwirq(data);
2e494cbd89c51d1 Roman Kisel 2025-03-07 2370
2e494cbd89c51d1 Roman Kisel 2025-03-07 2371 vmbus_irq = irq;
2e494cbd89c51d1 Roman Kisel 2025-03-07 2372 vmbus_interrupt = hwirq;
2e494cbd89c51d1 Roman Kisel 2025-03-07 2373 pr_debug("VMBus virq %d, hwirq %d\n", vmbus_irq, vmbus_interrupt);
2e494cbd89c51d1 Roman Kisel 2025-03-07 2374
2e494cbd89c51d1 Roman Kisel 2025-03-07 2375 return 0;
2e494cbd89c51d1 Roman Kisel 2025-03-07 2376 }
2e494cbd89c51d1 Roman Kisel 2025-03-07 2377
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-03-13 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 15:57 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-07 22:02 [PATCH hyperv-next v5 00/11] arm64: hyperv: Support Virtual Trust Level Boot Roman Kisel
2025-03-07 22:03 ` [PATCH hyperv-next v5 08/11] Drivers: hv: vmbus: Get the IRQ number from DeviceTree Roman Kisel
2025-03-08 21:11 ` Arnd Bergmann
2025-03-10 17:36 ` Roman Kisel
2025-03-10 23:09 ` Michael Kelley
2025-03-13 18:31 ` Dan Carpenter
2025-03-13 18:35 ` Roman Kisel
2025-03-13 18:44 ` Rob Herring
2025-03-13 18:46 ` Roman Kisel
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=202503132345.uKNehsnm-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.