[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbkPX3cX9VDoGx9LMLPgDFxwVbWQuKuaSyED5Nek0ATRQ@mail.gmail.com>
Date: Tue, 12 May 2020 14:35:17 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Aman Sharma <amanharitsh123@...il.com>,
linux-pci <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: [PATCH v2 0/2] PCI: Check for platform_get_irq() failure consistently
On Sat, May 2, 2020 at 12:41 AM Bjorn Helgaas <helgaas@...nel.org> wrote:
> From: Bjorn Helgaas <bhelgaas@...gle.com>
>
> All callers of platform_get_irq() and related functions interpret a
> negative return value as an error. A few also interpret zero as an error.
>
> platform_get_irq() should return either a negative error number or a valid
> non-zero IRQ, so there's no need to check for zero.
>
> This series:
>
> - Extends the platform_get_irq() function comment to say it returns a
> non-zero IRQ number or a negative error number.
>
> - Adds a WARN() if platform_get_irq() ever *does* return zero (this would
> be a bug in the underlying arch code, and most callers are not prepared
> for this).
>
> - Updates drivers/pci/ to check consistently using "irq < 0".
>
> This is based on Aman's series [1]. I propose to merge this via the PCI
> tree, given acks from Greg and Thomas.
>
> [1] https://lore.kernel.org/r/cover.1583952275.git.amanharitsh123@gmail.com
Makes sense to me.
Acked-by: Linus Walleij <linus.walleij@...aro.org>
for the series.
Yours,
Linus Walleij
Powered by blists - more mailing lists