From: Thomas Gleixner <tglx@linutronix.de>
To: "Aaron Kling via B4 Relay"
<devnull+webgeek1234.gmail.com@kernel.org>,
"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: Re: [PATCH v2 1/3] irqdomain: Export irq_domain_free_irqs
Date: Tue, 29 Apr 2025 08:36:19 +0200 [thread overview]
Message-ID: <877c33qxss.ffs@tglx> (raw)
In-Reply-To: <20250428-pci-tegra-module-v2-1-c11a4b912446@gmail.com>
On Mon, Apr 28 2025 at 20:05, Aaron Kling via wrote:
$subject: .... irq_domain_free_irqs()
> From: Aaron Kling <webgeek1234@gmail.com>
>
> Add export for irq_domain_free_irqs() so that we can allow drivers like
> the pci-tegra driver to be loadable as a module.
Export irq_domain_free_irqs() to allow PCI/MSI drivers like pci-tegra to
be built as a module.
See https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#changelog
With that addressed:
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2025-04-29 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 1:05 [PATCH v2 0/3] PCI: tegra: Allow building as a module Aaron Kling via B4 Relay
2025-04-29 1:05 ` [PATCH v2 1/3] irqdomain: Export irq_domain_free_irqs Aaron Kling via B4 Relay
2025-04-29 6:36 ` Thomas Gleixner [this message]
2025-04-29 1:05 ` [PATCH v2 2/3] cpuidle: tegra: Export tegra_cpuidle_pcie_irqs_in_use Aaron Kling via B4 Relay
2025-04-29 1:05 ` [PATCH v2 3/3] PCI: tegra: Allow building as a module Aaron Kling via B4 Relay
2025-05-02 15:33 ` Manivannan Sadhasivam
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=877c33qxss.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bhelgaas@google.com \
--cc=daniel.lezcano@linaro.org \
--cc=devnull+webgeek1234.gmail.com@kernel.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=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).