From: Manivannan Sadhasivam <mani@kernel.org>
To: lpieralisi@kernel.org, kwilczynski@kernel.org, robh@kernel.org,
bhelgaas@google.com, jingoohan1@gmail.com,
christian.bruel@foss.st.com, quic_wenbyao@quicinc.com,
inochiama@gmail.com, mayank.rana@oss.qualcomm.com,
thippeswamy.havalige@amd.com, shradha.t@samsung.com,
cassel@kernel.org, kishon@kernel.org,
sergio.paracuellos@gmail.com, 18255117159@163.com,
rongqianfeng@vivo.com, jirislaby@kernel.org,
Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, srk@ti.com
Subject: Re: [PATCH v3 0/4] PCI: Keystone: Enable loadable module support
Date: Mon, 22 Sep 2025 13:56:08 +0530 [thread overview]
Message-ID: <175852954905.18749.5091036983349477093.b4-ty@kernel.org> (raw)
In-Reply-To: <20250922071222.2814937-1-s-vadapalli@ti.com>
On Mon, 22 Sep 2025 12:42:12 +0530, Siddharth Vadapalli wrote:
> This series enables support for the 'pci-keystone.c' driver to be built
> as a loadable module. The motivation for the series is that PCIe is not
> a necessity for booting Linux due to which the 'pci-keystone.c' driver
> does not need to be built-in.
>
> Series is based on commit
> dc72930fe22e Merge branch 'pci/misc'
> of pci/next.
>
> [...]
Applied, thanks!
[1/4] PCI: Export pci_get_host_bridge_device() for use by pci-keystone
commit: c514ba0fa8938ae09370beecb77257868c1568a7
[2/4] PCI: dwc: Export dw_pcie_allocate_domains() and dw_pcie_ep_raise_msix_irq()
commit: db9ff606a5535aee94bf41682f03aba500ff3ad6
[3/4] PCI: keystone: Exit ks_pcie_probe() for invalid mode
commit: 76d23c87a3e06af003ae3a08053279d06141c716
[4/4] PCI: keystone: Add support to build as a loadable module
commit: e82d56b5f3844189f2b2240b1c3eaeeafc8f1fd2
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
next prev parent reply other threads:[~2025-09-22 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 7:12 Siddharth Vadapalli
2025-09-22 7:12 ` [PATCH v3 1/4] PCI: Export pci_get_host_bridge_device() for use by pci-keystone Siddharth Vadapalli
2025-09-22 7:12 ` [PATCH v3 2/4] PCI: dwc: Export dw_pcie_allocate_domains() and dw_pcie_ep_raise_msix_irq() Siddharth Vadapalli
2025-09-22 7:12 ` [PATCH v3 3/4] PCI: keystone: Exit ks_pcie_probe() for invalid mode Siddharth Vadapalli
2025-09-22 7:12 ` [PATCH v3 4/4] PCI: keystone: Add support to build as a loadable module Siddharth Vadapalli
2025-09-22 8:26 ` Manivannan Sadhasivam [this message]
2025-09-22 8:32 ` [PATCH v3 0/4] PCI: Keystone: Enable loadable module support Manivannan Sadhasivam
2025-09-22 9:25 ` Siddharth Vadapalli
2025-09-22 11:17 ` Manivannan Sadhasivam
2025-09-22 12:49 ` Siddharth Vadapalli
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=175852954905.18749.5091036983349477093.b4-ty@kernel.org \
--to=mani@kernel.org \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=christian.bruel@foss.st.com \
--cc=inochiama@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=jirislaby@kernel.org \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mayank.rana@oss.qualcomm.com \
--cc=quic_wenbyao@quicinc.com \
--cc=robh@kernel.org \
--cc=rongqianfeng@vivo.com \
--cc=s-vadapalli@ti.com \
--cc=sergio.paracuellos@gmail.com \
--cc=shradha.t@samsung.com \
--cc=srk@ti.com \
--cc=thippeswamy.havalige@amd.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®