[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200609155124.GB2597@infradead.org>
Date: Tue, 9 Jun 2020 08:51:24 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Piotr Stankiewicz <piotr.stankiewicz@...el.com>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org,
Kurt Schwemmer <kurt.schwemmer@...rosemi.com>,
Logan Gunthorpe <logang@...tatee.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Andy Shevchenko <andriy.shevchenko@...el.com>,
Olof Johansson <olof@...om.net>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
Kelvin Cao <kelvin.cao@...rochip.com>,
Wesley Sheng <wesley.sheng@...rochip.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Krzysztof Wilczynski <kw@...ux.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 03/15] PCI: Use PCI_IRQ_MSI_TYPES where appropriate
On Tue, Jun 09, 2020 at 11:16:46AM +0200, Piotr Stankiewicz wrote:
> Seeing as there is shorthand available to use when asking for any type
> of interrupt, or any type of message signalled interrupt, leverage it.
>
> Signed-off-by: Piotr Stankiewicz <piotr.stankiewicz@...el.com>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@...el.com>
> Reviewed-by: Logan Gunthorpe <logang@...tatee.com>
The patch actually adding PCI_IRQ_MSI_TYPES still didn't show up on
linux-pci.
But from the person who added PCI_IRQ_*:
NAK to the whole concept of PCI_IRQ_MSI_TYPES, I think this just makes
the code a lot more confusing. Especially with the new IMS interrupt
type, which really is a MSI-like interrupt but certainly shouldn't be
added to this mask.
Powered by blists - more mailing lists