From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [PATCH v2 4/5] clk: tegra: Add stubs needed for compile testing
Date: Mon, 12 Jul 2021 03:03:21 +0300 [thread overview]
Message-ID: <20210712000322.4224-5-digetx@gmail.com> (raw)
In-Reply-To: <20210712000322.4224-1-digetx@gmail.com>
Add stubs needed for compile-testing of tegra-cpuidle driver.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
include/linux/clk/tegra.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/include/linux/clk/tegra.h b/include/linux/clk/tegra.h
index d128ad1570aa..9bd06d8a5436 100644
--- a/include/linux/clk/tegra.h
+++ b/include/linux/clk/tegra.h
@@ -42,7 +42,11 @@ struct tegra_cpu_car_ops {
#endif
};
+#ifdef CONFIG_ARCH_TEGRA
extern struct tegra_cpu_car_ops *tegra_cpu_car_ops;
+#else
+static struct tegra_cpu_car_ops *tegra_cpu_car_ops __maybe_unused;
+#endif
static inline void tegra_wait_cpu_in_reset(u32 cpu)
{
--
2.32.0
next prev parent reply other threads:[~2021-07-12 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 0:03 [PATCH v2 0/5] Compile-test NVIDIA Tegra CPUIDLE driver Dmitry Osipenko
2021-07-12 0:03 ` [PATCH v2 1/5] soc/tegra: fuse: Add stubs needed for compile testing Dmitry Osipenko
2021-07-12 0:03 ` [PATCH v2 2/5] soc/tegra: irq: " Dmitry Osipenko
2021-07-12 0:03 ` [PATCH v2 3/5] soc/tegra: pm: Make stubs usable " Dmitry Osipenko
2021-07-12 0:03 ` Dmitry Osipenko [this message]
2021-07-12 0:03 ` [PATCH v2 5/5] cpuidle: tegra: Enable " Dmitry Osipenko
2021-08-16 15:32 ` Dmitry Osipenko
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=20210712000322.4224-5-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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 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).