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 v5 0/3] PCI: tegra: Allow building as a module
Date: Tue, 06 May 2025 09:42:31 +0200 [thread overview]
Message-ID: <87ikmenq1k.ffs@tglx> (raw)
In-Reply-To: <20250505-pci-tegra-module-v5-0-827aaac998ba@gmail.com>
On Mon, May 05 2025 at 18:17, Aaron Kling via wrote:
> - Copy commit message exactly word for word on patch 1, as required by reviewer
That's not what I asked for at all. I asked you to read _ALL_ feedback I
gave you. I give up now.
prev parent reply other threads:[~2025-05-06 7:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 23:17 [PATCH v5 0/3] PCI: tegra: Allow building as a module Aaron Kling
2025-05-05 23:17 ` Aaron Kling via B4 Relay
2025-05-05 23:17 ` [PATCH v5 1/3] irqdomain: Export irq_domain_free_irqs Aaron Kling
2025-05-05 23:17 ` Aaron Kling via B4 Relay
2025-05-05 23:17 ` [PATCH v5 2/3] cpuidle: tegra: Export tegra_cpuidle_pcie_irqs_in_use Aaron Kling
2025-05-05 23:17 ` Aaron Kling via B4 Relay
2025-05-05 23:17 ` [PATCH v5 3/3] PCI: tegra: Allow building as a module Aaron Kling
2025-05-05 23:17 ` Aaron Kling via B4 Relay
2025-05-07 19:54 ` kernel test robot
2025-05-06 7:42 ` Thomas Gleixner [this message]
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=87ikmenq1k.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 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.