From: helgaas@kernel.org (Bjorn Helgaas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/6] Xilinx AXI PCIe Host Bridge driver fixes
Date: Thu, 25 Feb 2016 09:59:11 -0600 [thread overview]
Message-ID: <20160225155911.GF8120@localhost> (raw)
In-Reply-To: <1454602213-967-1-git-send-email-paul.burton@imgtec.com>
Hi Paul,
On Thu, Feb 04, 2016 at 04:10:07PM +0000, Paul Burton wrote:
> This series fixes a number of issues found using the Xilinx AXI PCIe
> Host Bridge IP on the Imagination Technologies MIPS Boston development
> board. It has been split out of the larger Boston board support series
> at Michal's request.
>
> Applies atop v4.5-rc2.
>
> Paul Burton (6):
> PCI: xilinx: Keep references to both IRQ domains
> PCI: xilinx: Unify INTx & MSI interrupt FIFO decode
> PCI: xilinx: Always clear interrupt decode register
> PCI: xilinx: Clear interrupt FIFO during probe
> PCI: xilinx: Fix INTX irq dispatch
> PCI: xilinx: Allow build on MIPS platforms
>
> drivers/pci/host/Kconfig | 2 +-
> drivers/pci/host/pcie-xilinx.c | 125 +++++++++++++++++++----------------------
Looks like Bharat has some IRQ concerns, so I'm guessing you'll be
posting a v4?
Bjorn
prev parent reply other threads:[~2016-02-25 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 16:10 [PATCH v3 0/6] Xilinx AXI PCIe Host Bridge driver fixes Paul Burton
2016-02-04 16:10 ` [PATCH v3 1/6] PCI: xilinx: Keep references to both IRQ domains Paul Burton
2016-02-04 16:10 ` [PATCH v3 2/6] PCI: xilinx: Unify INTx & MSI interrupt FIFO decode Paul Burton
2016-02-11 5:42 ` Bharat Kumar Gogada
2016-02-11 5:50 ` Bharat Kumar Gogada
2016-02-04 16:10 ` [PATCH v3 3/6] PCI: xilinx: Always clear interrupt decode register Paul Burton
2016-02-04 16:10 ` [PATCH v3 4/6] PCI: xilinx: Clear interrupt FIFO during probe Paul Burton
2016-02-11 6:20 ` Bharat Kumar Gogada
2016-02-04 16:10 ` [PATCH v3 5/6] PCI: xilinx: Fix INTX irq dispatch Paul Burton
2016-02-25 15:59 ` Bjorn Helgaas [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=20160225155911.GF8120@localhost \
--to=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).