From: Michal Simek <monstr@monstr.eu>
To: Bjorn Helgaas <helgaas@kernel.org>,
Michal Simek <michal.simek@xilinx.com>
Cc: linux-kernel@vger.kernel.org, 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 14:53:47 +0200 [thread overview]
Message-ID: <a23f5c0c-6f0b-69bb-78d4-553986157dcd@monstr.eu> (raw)
In-Reply-To: <20191008124723.GA161444@google.com>
On 08. 10. 19 14:47, Bjorn Helgaas wrote:
> 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.
I was splitting them based on RISC-V case to follow this pattern.
Anyway I will send v2 and please pick it via your tree.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
prev parent reply other threads:[~2019-10-08 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 10:39 Michal Simek
2019-10-08 12:47 ` Bjorn Helgaas
2019-10-08 12:53 ` Michal Simek [this message]
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=a23f5c0c-6f0b-69bb-78d4-553986157dcd@monstr.eu \
--to=monstr@monstr.eu \
--cc=git@xilinx.com \
--cc=helgaas@kernel.org \
--cc=kuldeep.dave@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michal.simek@xilinx.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
all inboxes | Powered by JetHome®