[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191017181937.7004-4-palmer@sifive.com>
Date: Thu, 17 Oct 2019 11:19:37 -0700
From: Palmer Dabbelt <palmer@...ive.com>
To: Christoph Hellwig <hch@...radead.org>, michal.simek@...inx.com,
helgaas@...nel.org
Cc: tony.luck@...el.com, fenghua.yu@...el.com,
heiko.carstens@...ibm.com, gor@...ux.ibm.com,
borntraeger@...ibm.com, bhelgaas@...gle.com, will@...nel.org,
Greg KH <gregkh@...uxfoundation.org>,
Palmer Dabbelt <palmer@...ive.com>,
kstewart@...uxfoundation.org, pbonzini@...hat.com,
firoz.khan@...aro.org, yamada.masahiro@...ionext.com,
longman@...hat.com, mingo@...nel.org, peterz@...radead.org,
linux-ia64@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-s390@...r.kernel.org, linux-pci@...r.kernel.org
Subject: [PATCH 3/3] pci: Default to PCI_MSI_IRQ_DOMAIN
As far as I can tell, the only reason there was an architecture
whitelist for PCI_MSI_IRQ_DOMAIN is because it requires msi.h. I've
built this for all the architectures that play nice with make.cross, but
I haven't boot tested it anywhere.
Signed-off-by: Palmer Dabbelt <palmer@...ive.com>
---
drivers/pci/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig
index a304f5ea11b9..77c1428cd945 100644
--- a/drivers/pci/Kconfig
+++ b/drivers/pci/Kconfig
@@ -52,7 +52,7 @@ config PCI_MSI
If you don't know what to do here, say Y.
config PCI_MSI_IRQ_DOMAIN
- def_bool ARC || ARM || ARM64 || X86 || RISCV
+ def_bool y
depends on PCI_MSI
select GENERIC_MSI_IRQ_DOMAIN
--
2.21.0
Powered by blists - more mailing lists