From: Aaron Kling <webgeek1234@gmail.com>
To: "Thomas Gleixner" <tglx@linutronix.de>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-tegra@vger.kernel.org, Aaron Kling <webgeek1234@gmail.com>
Subject: [PATCH 2/2] PCI: tegra: Allow building as a module
Date: Sun, 20 Apr 2025 21:59:06 -0500 [thread overview]
Message-ID: <20250420-pci-tegra-module-v1-2-c0a1f831354a@gmail.com> (raw)
In-Reply-To: <20250420-pci-tegra-module-v1-0-c0a1f831354a@gmail.com>
The driver works fine as a module, so allow building as such.
Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
drivers/pci/controller/Kconfig | 2 +-
drivers/pci/controller/pci-tegra.c | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/pci/controller/Kconfig b/drivers/pci/controller/Kconfig
index 9800b768105402d6dd1ba4b134c2ec23da6e4201..a9164dd2eccaead5ae9348c24a5ad75fcb40f507 100644
--- a/drivers/pci/controller/Kconfig
+++ b/drivers/pci/controller/Kconfig
@@ -224,7 +224,7 @@ config PCI_HYPERV_INTERFACE
driver.
config PCI_TEGRA
- bool "NVIDIA Tegra PCIe controller"
+ tristate "NVIDIA Tegra PCIe controller"
depends on ARCH_TEGRA || COMPILE_TEST
depends on PCI_MSI
help
diff --git a/drivers/pci/controller/pci-tegra.c b/drivers/pci/controller/pci-tegra.c
index b3cdbc5927de3742161310610dc5dcb836f5dd69..c260842695f2e983ae48fd52b43f62dbb9fb5dd3 100644
--- a/drivers/pci/controller/pci-tegra.c
+++ b/drivers/pci/controller/pci-tegra.c
@@ -2803,3 +2803,6 @@ static struct platform_driver tegra_pcie_driver = {
.remove = tegra_pcie_remove,
};
module_platform_driver(tegra_pcie_driver);
+MODULE_AUTHOR("Thierry Reding <treding@nvidia.com>");
+MODULE_DESCRIPTION("NVIDIA PCI host controller driver");
+MODULE_LICENSE("GPL");
--
2.48.1
WARNING: multiple messages have this Message-ID (diff)
From: Aaron Kling via B4 Relay <devnull+webgeek1234.gmail.com@kernel.org>
To: "Thomas Gleixner" <tglx@linutronix.de>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-tegra@vger.kernel.org, Aaron Kling <webgeek1234@gmail.com>
Subject: [PATCH 2/2] PCI: tegra: Allow building as a module
Date: Sun, 20 Apr 2025 21:59:06 -0500 [thread overview]
Message-ID: <20250420-pci-tegra-module-v1-2-c0a1f831354a@gmail.com> (raw)
In-Reply-To: <20250420-pci-tegra-module-v1-0-c0a1f831354a@gmail.com>
From: Aaron Kling <webgeek1234@gmail.com>
The driver works fine as a module, so allow building as such.
Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
drivers/pci/controller/Kconfig | 2 +-
drivers/pci/controller/pci-tegra.c | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/pci/controller/Kconfig b/drivers/pci/controller/Kconfig
index 9800b768105402d6dd1ba4b134c2ec23da6e4201..a9164dd2eccaead5ae9348c24a5ad75fcb40f507 100644
--- a/drivers/pci/controller/Kconfig
+++ b/drivers/pci/controller/Kconfig
@@ -224,7 +224,7 @@ config PCI_HYPERV_INTERFACE
driver.
config PCI_TEGRA
- bool "NVIDIA Tegra PCIe controller"
+ tristate "NVIDIA Tegra PCIe controller"
depends on ARCH_TEGRA || COMPILE_TEST
depends on PCI_MSI
help
diff --git a/drivers/pci/controller/pci-tegra.c b/drivers/pci/controller/pci-tegra.c
index b3cdbc5927de3742161310610dc5dcb836f5dd69..c260842695f2e983ae48fd52b43f62dbb9fb5dd3 100644
--- a/drivers/pci/controller/pci-tegra.c
+++ b/drivers/pci/controller/pci-tegra.c
@@ -2803,3 +2803,6 @@ static struct platform_driver tegra_pcie_driver = {
.remove = tegra_pcie_remove,
};
module_platform_driver(tegra_pcie_driver);
+MODULE_AUTHOR("Thierry Reding <treding@nvidia.com>");
+MODULE_DESCRIPTION("NVIDIA PCI host controller driver");
+MODULE_LICENSE("GPL");
--
2.48.1
next prev parent reply other threads:[~2025-04-21 2:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 2:59 [PATCH 0/2] PCI: tegra: Allow building as a module Aaron Kling
2025-04-21 2:59 ` Aaron Kling via B4 Relay
2025-04-21 2:59 ` [PATCH 1/2] irqdomain: Export irq_domain_free_irqs Aaron Kling
2025-04-21 2:59 ` Aaron Kling via B4 Relay
2025-04-21 2:59 ` Aaron Kling [this message]
2025-04-21 2:59 ` [PATCH 2/2] PCI: tegra: Allow building as a module Aaron Kling via B4 Relay
2025-04-21 7:52 ` Manivannan Sadhasivam
2025-04-21 8:09 ` Aaron Kling
2025-04-21 8:54 ` Manivannan Sadhasivam
2025-04-21 16:33 ` Aaron Kling
2025-04-27 15:57 ` Manivannan Sadhasivam
2025-04-28 22:39 ` Aaron Kling
2025-04-29 1:03 ` Aaron Kling
2025-05-02 15:31 ` Manivannan Sadhasivam
2025-04-21 12:57 ` kernel test robot
[not found] ` <CABr+WT=4r46L4x-Hez_uqxw1aXmG6Wda0HxCJf_m+0Jj5B8JRQ@mail.gmail.com>
2025-04-21 16:38 ` Aaron Kling
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=20250420-pci-tegra-module-v1-2-c0a1f831354a@gmail.com \
--to=webgeek1234@gmail.com \
--cc=bhelgaas@google.com \
--cc=jonathanh@nvidia.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.