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>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org,
Aaron Kling <webgeek1234@gmail.com>
Subject: [PATCH v4 0/4] PCI: tegra: Allow building as a module
Date: Mon, 05 May 2025 09:58:57 -0500 [thread overview]
Message-ID: <20250505-pci-tegra-module-v4-0-088b552c4b1a@gmail.com> (raw)
Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
Changes in v4:
- Updated commit messages for patches 1 and 2, per review
- Link to v3: https://lore.kernel.org/r/20250502-pci-tegra-module-v3-0-556a49732d70@gmail.com
Changes in v3:
- Add patch to drop remove callback, per request
- Link to v2: https://lore.kernel.org/r/20250428-pci-tegra-module-v2-0-c11a4b912446@gmail.com
Changes in v2:
- Add patch to export tegra_cpuidle_pcie_irqs_in_use as required when
building pci-tegra as a module for arm
- Drop module exit to prevent module unloading, as requested
- Link to v1: https://lore.kernel.org/r/20250420-pci-tegra-module-v1-0-c0a1f831354a@gmail.com
---
Aaron Kling (4):
irqdomain: Export irq_domain_free_irqs
cpuidle: tegra: Export tegra_cpuidle_pcie_irqs_in_use
PCI: tegra: Allow building as a module
PCI: tegra: Drop unused remove callback
drivers/cpuidle/cpuidle-tegra.c | 1 +
drivers/pci/controller/Kconfig | 2 +-
drivers/pci/controller/pci-tegra.c | 24 ++++++------------------
kernel/irq/irqdomain.c | 1 +
4 files changed, 9 insertions(+), 19 deletions(-)
---
base-commit: 18352e73612d60b81790d2437845276ae499b64a
change-id: 20250313-pci-tegra-module-7cbd1c5e70af
Best regards,
--
Aaron Kling <webgeek1234@gmail.com>
next reply other threads:[~2025-05-05 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 14:58 Aaron Kling via B4 Relay [this message]
2025-05-05 14:58 ` [PATCH v4 1/4] irqdomain: Export irq_domain_free_irqs Aaron Kling via B4 Relay
2025-05-05 22:33 ` Thomas Gleixner
2025-05-05 14:58 ` [PATCH v4 2/4] cpuidle: tegra: Export tegra_cpuidle_pcie_irqs_in_use Aaron Kling via B4 Relay
2025-05-05 14:59 ` [PATCH v4 3/4] PCI: tegra: Allow building as a module Aaron Kling via B4 Relay
2025-05-05 14:59 ` [PATCH v4 4/4] PCI: tegra: Drop unused remove callback Aaron Kling via B4 Relay
2025-05-05 16:31 ` Manivannan Sadhasivam
2025-05-05 16:43 ` Aaron Kling
2025-05-05 16:48 ` Manivannan Sadhasivam
2025-05-05 16:59 ` Aaron Kling
2025-05-10 6:24 ` Manivannan Sadhasivam
2025-05-11 14:53 ` 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=20250505-pci-tegra-module-v4-0-088b552c4b1a@gmail.com \
--to=devnull+webgeek1234.gmail.com@kernel.org \
--cc=bhelgaas@google.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=webgeek1234@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 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).