All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Kisel <romank@linux.microsoft.com>
To: Dan Carpenter <dan.carpenter@linaro.org>,
	oe-kbuild@lists.linux.dev, arnd@arndb.de, bhelgaas@google.com,
	bp@alien8.de, catalin.marinas@arm.com, conor+dt@kernel.org,
	dave.hansen@linux.intel.com, decui@microsoft.com,
	haiyangz@microsoft.com, hpa@zytor.com, joey.gouly@arm.com,
	krzk+dt@kernel.org, kw@linux.com, kys@microsoft.com,
	lenb@kernel.org, lpieralisi@kernel.org,
	manivannan.sadhasivam@linaro.org, mark.rutland@arm.com,
	maz@kernel.org, mingo@redhat.com, oliver.upton@linux.dev,
	rafael@kernel.org, robh@kernel.org, ssengar@linux.microsoft.com,
	sudeep.holla@arm.com, suzuki.poulose@arm.com, tglx@linutronix.de,
	wei.liu@kernel.org, will@kernel.org, yuzenghui@huawei.com,
	devicetree@vger.kernel.org
Cc: lkp@intel.com, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH hyperv-next v5 08/11] Drivers: hv: vmbus: Get the IRQ number from DeviceTree
Date: Thu, 13 Mar 2025 11:35:19 -0700	[thread overview]
Message-ID: <cfb17505-fb4a-42c4-91cf-de636a8efa87@linux.microsoft.com> (raw)
In-Reply-To: <1283ab3a-a66b-4fe2-9ba4-8d5972daa89b@stanley.mountain>



On 3/13/2025 11:31 AM, Dan Carpenter wrote:
> Hi Roman,

Hi Dan,

Appreciate helping with that very much!

-- 
Thank you,
Roman

> 
> kernel test robot noticed the following build warnings:
> 
> 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
> 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 <dan.carpenter@linaro.org>
> | 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
> 
> 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;
> 
> You can delete this if statement.  It's dead code.  See the comment
> next to platform_get_irq().  I wrote a blog about the history of
> this:
> https://staticthinking.wordpress.com/2023/08/07/writing-a-check-for-zero-irq-error-codes/
> 
> 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  }
> 

  reply	other threads:[~2025-03-13 18:35 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 22:02 [PATCH hyperv-next v5 00/11] arm64: hyperv: Support Virtual Trust Level Boot Roman Kisel
2025-03-07 22:02 ` [PATCH hyperv-next v5 01/11] arm64: kvm, smccc: Introduce and use API for detectting hypervisor presence Roman Kisel
2025-03-08 21:08   ` Arnd Bergmann
2025-03-10 21:16   ` Michael Kelley
2025-03-10 21:54     ` Roman Kisel
2025-03-12 14:07   ` kernel test robot
2025-03-12 21:18   ` kernel test robot
2025-03-07 22:02 ` [PATCH hyperv-next v5 02/11] arm64: hyperv: Use SMCCC to detect " Roman Kisel
2025-03-10 21:17   ` Michael Kelley
2025-03-07 22:02 ` [PATCH hyperv-next v5 03/11] Drivers: hv: Enable VTL mode for arm64 Roman Kisel
2025-03-08 21:05   ` Arnd Bergmann
2025-03-10 17:35     ` Roman Kisel
2025-03-10 21:01     ` Michael Kelley
2025-03-10 21:20       ` Arnd Bergmann
2025-03-10 22:18         ` Michael Kelley
2025-03-12 18:33           ` Roman Kisel
2025-03-12 20:25             ` Arnd Bergmann
2025-03-12 21:21               ` Roman Kisel
2025-03-13  5:10                 ` Michael Kelley
2025-03-12 20:31             ` Wei Liu
2025-03-12 21:30               ` Roman Kisel
2025-03-07 22:02 ` [PATCH hyperv-next v5 04/11] Drivers: hv: Provide arch-neutral implementation of get_vtl() Roman Kisel
2025-03-10 13:44   ` Tianyu Lan
2025-03-07 22:02 ` [PATCH hyperv-next v5 05/11] arm64: hyperv: Initialize the Virtual Trust Level field Roman Kisel
2025-03-10 23:07   ` Michael Kelley
2025-03-07 22:02 ` [PATCH hyperv-next v5 06/11] arm64, x86: hyperv: Report the VTL the system boots in Roman Kisel
2025-03-10  0:31   ` Wei Liu
2025-03-10 16:42     ` Roman Kisel
2025-03-10 16:53       ` Wei Liu
2025-03-10 17:20         ` Roman Kisel
2025-03-07 22:02 ` [PATCH hyperv-next v5 07/11] dt-bindings: microsoft,vmbus: Add interrupts and DMA coherence Roman Kisel
2025-03-10  9:28   ` Krzysztof Kozlowski
2025-03-10 17:05     ` Roman Kisel
2025-03-10 17:40       ` Krzysztof Kozlowski
2025-03-10 18:07         ` Roman Kisel
2025-03-10 21:17           ` Krzysztof Kozlowski
2025-03-10 21:51             ` 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 [this message]
2025-03-13 18:44   ` Rob Herring
2025-03-13 18:46     ` Roman Kisel
2025-03-07 22:03 ` [PATCH hyperv-next v5 09/11] Drivers: hv: vmbus: Introduce hv_get_vmbus_root_device() Roman Kisel
2025-03-10 13:41   ` Tianyu Lan
2025-03-10 17:09     ` Roman Kisel
2025-03-10 23:12   ` Michael Kelley
2025-03-07 22:03 ` [PATCH hyperv-next v5 10/11] ACPI: irq: Introduce acpi_get_gsi_dispatcher() Roman Kisel
2025-03-10 23:26   ` Michael Kelley
2025-03-07 22:03 ` [PATCH hyperv-next v5 11/11] PCI: hv: Get vPCI MSI IRQ domain from DeviceTree Roman Kisel
2025-03-10 16:41   ` Bjorn Helgaas
2025-03-10 17:15     ` Roman Kisel
2025-03-10 23:42   ` Michael Kelley
  -- strict thread matches above, loose matches on Subject: below --
2025-03-13 15:57 [PATCH hyperv-next v5 08/11] Drivers: hv: vmbus: Get the IRQ number " kernel test robot

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=cfb17505-fb4a-42c4-91cf-de636a8efa87@linux.microsoft.com \
    --to=romank@linux.microsoft.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=decui@microsoft.com \
    --cc=devicetree@vger.kernel.org \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=joey.gouly@arm.com \
    --cc=krzk+dt@kernel.org \
    --cc=kw@linux.com \
    --cc=kys@microsoft.com \
    --cc=lenb@kernel.org \
    --cc=lkp@intel.com \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=oe-kbuild@lists.linux.dev \
    --cc=oliver.upton@linux.dev \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=ssengar@linux.microsoft.com \
    --cc=sudeep.holla@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tglx@linutronix.de \
    --cc=wei.liu@kernel.org \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.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 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.