From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: conor.dooley@microchip.com, kw@linux.com, robh@kernel.org,
bhelgaas@google.com, linux-riscv@lists.infradead.org,
linux-pci@vger.kernel.org, daire.mcnamara@microchip.com
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>
Subject: Re: [PATCH v3 0/7] PCI: microchip: Fixes and clean-ups
Date: Tue, 8 Aug 2023 13:02:37 +0200 [thread overview]
Message-ID: <169149233963.79399.5232296870054239065.b4-ty@kernel.org> (raw)
In-Reply-To: <20230728131401.1615724-1-daire.mcnamara@microchip.com>
On Fri, 28 Jul 2023 14:13:54 +0100, daire.mcnamara@microchip.com wrote:
> This patch series contains fixes and clean-ups for the Microchip PolarFire SoC PCIe driver
>
> These patches are extracted from the link below to separate them from the outbound and inbound
> range handling which is taking considerable time.
> Link: https://lore.kernel.org/linux-riscv/20230111125323.1911373-1-daire.mcnamara@microchip.com/
>
> Resending with correct e-mail address list
>
> [...]
Applied to controller/microchip, thanks!
[1/7] PCI: microchip: Correct the DED and SEC interrupt bit offsets
https://git.kernel.org/pci/pci/c/6d473a5a2613
[2/7] PCI: microchip: Enable building driver as a module
https://git.kernel.org/pci/pci/c/2e245bc8a2ab
[3/7] PCI: microchip: Align register, offset, and mask names with hw docs
https://git.kernel.org/pci/pci/c/4d6bf4c49578
[4/7] PCI: microchip: Enable event handlers to access bridge and ctrl ptrs
https://git.kernel.org/pci/pci/c/d1d6a0c9e79c
[5/7] PCI: microchip: Clean up initialisation of interrupts
https://git.kernel.org/pci/pci/c/4f0b91247f78
[6/7] PCI: microchip: Gather MSI information from hardware config registers
https://git.kernel.org/pci/pci/c/1abb722888fd
[7/7] PCI: microchip: Re-partition code between probe() and init()
https://git.kernel.org/pci/pci/c/bac406c34fbc
Thanks,
Lorenzo
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-08-08 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 13:13 [PATCH v3 0/7] PCI: microchip: Fixes and clean-ups daire.mcnamara
2023-07-28 13:13 ` [PATCH v3 1/7] PCI: microchip: Correct the DED and SEC interrupt bit offsets daire.mcnamara
2023-07-28 13:13 ` [PATCH v3 2/7] PCI: microchip: Enable building driver as a module daire.mcnamara
2023-07-28 13:13 ` [PATCH v3 3/7] PCI: microchip: Align register, offset, and mask names with hw docs daire.mcnamara
2023-07-28 13:13 ` [PATCH v3 4/7] PCI: microchip: Enable event handlers to access bridge and ctrl ptrs daire.mcnamara
2023-07-28 13:13 ` [PATCH v3 5/7] PCI: microchip: Clean up initialisation of interrupts daire.mcnamara
2023-07-28 13:14 ` [PATCH v3 6/7] PCI: microchip: Gather MSI information from hardware config registers daire.mcnamara
2023-07-28 13:14 ` [PATCH v3 7/7] PCI: microchip: Re-partition code between probe() and init() daire.mcnamara
2024-05-30 16:42 ` Bjorn Helgaas
2023-08-08 11:02 ` Lorenzo Pieralisi [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-28 12:11 [PATCH v3 0/7] PCI: microchip: Fixes and clean-ups daire.mcnamara
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=169149233963.79399.5232296870054239065.b4-ty@kernel.org \
--to=lpieralisi@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.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