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 v1 0/5] Compile-test NVIDIA Tegra CPUIDLE driver
Date: Mon, 7 Jun 2021 01:28:12 +0300 [thread overview]
Message-ID: <20210606222817.12388-1-digetx@gmail.com> (raw)
Add couple missing stubs needed for compile-testing of tegra-cpuidle
driver and enable the compile-testing.
Dmitry Osipenko (5):
soc/tegra: fuse: Add stubs needed for compile testing
soc/tegra: irq: Add stubs needed for compile testing
soc/tegra: pm: Make stubs usable for compile testing
clk: tegra: Add stubs needed for compile testing
cpuidle: tegra: Enable compile testing
drivers/cpuidle/Kconfig.arm | 2 +-
include/linux/clk/tegra.h | 4 ++++
include/soc/tegra/fuse.h | 31 ++++++++++++++++++++++++++-----
include/soc/tegra/irq.h | 9 ++++++++-
include/soc/tegra/pm.h | 2 +-
5 files changed, 40 insertions(+), 8 deletions(-)
--
2.30.2
next reply other threads:[~2021-06-06 22:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 22:28 Dmitry Osipenko [this message]
2021-06-06 22:28 ` [PATCH v1 1/5] soc/tegra: fuse: Add stubs needed for compile testing Dmitry Osipenko
2021-06-06 22:28 ` [PATCH v1 2/5] soc/tegra: irq: " Dmitry Osipenko
2021-06-16 19:06 ` Daniel Lezcano
2021-06-16 19:17 ` Dmitry Osipenko
2021-06-16 19:18 ` Daniel Lezcano
2021-06-06 22:28 ` [PATCH v1 3/5] soc/tegra: pm: Make stubs usable " Dmitry Osipenko
2021-06-06 22:28 ` [PATCH v1 4/5] clk: tegra: Add stubs needed " Dmitry Osipenko
2021-06-16 19:08 ` Daniel Lezcano
2021-06-16 19:35 ` Dmitry Osipenko
2021-06-06 22:28 ` [PATCH v1 5/5] cpuidle: tegra: Enable " Dmitry Osipenko
2021-06-16 7:37 ` kernel test robot
2021-06-16 19:24 ` Dmitry Osipenko
2021-06-16 19:45 ` 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=20210606222817.12388-1-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