From: Bjorn Helgaas <helgaas@kernel.org>
To: Michal Simek <michal.simek@xilinx.com>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu, git@xilinx.com,
Kuldeep Dave <kuldeep.dave@xilinx.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/MSI: Enable PCI_MSI_IRQ_DOMAIN support for Microblaze
Date: Tue, 8 Oct 2019 07:47:23 -0500 [thread overview]
Message-ID: <20191008124723.GA161444@google.com> (raw)
In-Reply-To: <e0ead31283c74254e8c02c0e5e5123277ed1f927.1570531159.git.michal.simek@xilinx.com>
On Tue, Oct 08, 2019 at 12:39:22PM +0200, Michal Simek wrote:
> From: Kuldeep Dave <kuldeep.dave@xilinx.com>
>
> Add Microblaze as an arch that supports PCI_MSI_IRQ_DOMAIN.
> Enabling msi.h generation is done by separate patch.
>
> Similar change was done by commit 2a9af0273c1c
> ("PCI/MSI: Enable PCI_MSI_IRQ_DOMAIN support for RISC-V")
>
> Signed-off-by: Kuldeep Dave <kuldeep.dave@xilinx.com>
> Signed-off-by: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> Arch part was sent here:
> https://lkml.org/lkml/2019/10/8/277
Can you please squash this drivers/pci/Kconfig change into the same
patch as the arch/microblaze patch mentioned above? That way there's
no ordering issue between the two patches. I'd be glad to merge it,
or you can add my ack and apply it via the Microblaze tree. Just let
me know which you prefer so I know whether to do something with this.
Sorry; I probably suggested the splitting in the first place for
RISC-V, but I think that was a mistake.
> ---
> drivers/pci/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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
> depends on PCI_MSI
> select GENERIC_MSI_IRQ_DOMAIN
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-10-08 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 10:39 [PATCH] PCI/MSI: Enable PCI_MSI_IRQ_DOMAIN support for Microblaze Michal Simek
2019-10-08 12:47 ` Bjorn Helgaas [this message]
2019-10-08 12:53 ` Michal Simek
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=20191008124723.GA161444@google.com \
--to=helgaas@kernel.org \
--cc=git@xilinx.com \
--cc=kuldeep.dave@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
/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