From: Aaron Kling via B4 Relay <devnull+webgeek1234.gmail.com@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Sumit Gupta" <sumitg@nvidia.com>,
"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>,
"Vidya Sagar" <vidyas@nvidia.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, Aaron Kling <webgeek1234@gmail.com>
Subject: [PATCH 0/2] (no cover subject)
Date: Mon, 24 Feb 2025 11:55:32 -0600 [thread overview]
Message-ID: <20250224-build-tegra234-v1-0-39e4e912f968@gmail.com> (raw)
When Tegra234 support was added to existing Tegra drivers, many of them
did not have the matching Kconfig entries updated to allow building for
the arch. A few of those have already been fixed. This series fixes a
couple more.
Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
Aaron Kling (2):
cpufreq: tegra194: Allow building for Tegra234
PCI: tegra194: Allow building for Tegra234
drivers/cpufreq/Kconfig.arm | 2 +-
drivers/pci/controller/dwc/Kconfig | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
---
base-commit: d082ecbc71e9e0bf49883ee4afd435a77a5101b6
change-id: 20250224-build-tegra234-c185bda9fd4a
Best regards,
--
Aaron Kling <webgeek1234@gmail.com>
next reply other threads:[~2025-02-24 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 17:55 Aaron Kling via B4 Relay [this message]
2025-02-24 17:55 ` [PATCH 1/2] cpufreq: tegra194: Allow building for Tegra234 Aaron Kling via B4 Relay
2025-02-24 17:55 ` [PATCH 2/2] PCI: " Aaron Kling via B4 Relay
2025-03-10 14:08 ` [PATCH 0/2] (no cover subject) Krzysztof Wilczyński
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=20250224-build-tegra234-v1-0-39e4e912f968@gmail.com \
--to=devnull+webgeek1234.gmail.com@kernel.org \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sumitg@nvidia.com \
--cc=vidyas@nvidia.com \
--cc=viresh.kumar@linaro.org \
--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