From: Bjorn Helgaas <helgaas@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org, monstr@monstr.eu, git@xilinx.com,
Kuldeep Dave <kuldeep.dave@xilinx.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Palmer Dabbelt <palmer@sifive.com>,
linux-pci@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Firoz Khan <firoz.khan@linaro.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2] PCI/MSI: Enable PCI_MSI_IRQ_DOMAIN support for Microblaze
Date: Mon, 14 Oct 2019 18:23:45 -0500 [thread overview]
Message-ID: <20191014232345.GA246093@google.com> (raw)
In-Reply-To: <20191008154652.GB7903@infradead.org>
On Tue, Oct 08, 2019 at 08:46:52AM -0700, Christoph Hellwig wrote:
> > diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig
> > index a304f5ea11b9..9d259372fbfd 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 ARC || ARM || ARM64 || X86 || RISCV || MICROBLAZE
>
> Can you find out what the actual dependency is so that we can
> automatically enabled this instead of the weird arch list?
Hi Michal, I'll wait for your response on whether it's feasible to do
something smarter than listing every arch here. Please ping here or
post a v3; since I marked this patch "Changed Requested" in patchwork,
it's fallen off my to-do list.
Bjorn
next prev parent reply other threads:[~2019-10-14 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 12:58 [PATCH v2] PCI/MSI: Enable PCI_MSI_IRQ_DOMAIN support for Microblaze Michal Simek
2019-10-08 15:46 ` Christoph Hellwig
2019-10-14 23:23 ` Bjorn Helgaas [this message]
2019-10-15 5:59 ` Michal Simek
2019-10-16 23:57 ` Palmer Dabbelt
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=20191014232345.GA246093@google.com \
--to=helgaas@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=firoz.khan@linaro.org \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=kuldeep.dave@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=will@kernel.org \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).