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: Re: [PATCH v2 5/5] cpuidle: tegra: Enable compile testing
Date: Mon, 16 Aug 2021 18:32:50 +0300 [thread overview]
Message-ID: <bae8fc99-b29e-0721-c37e-a29898c7cba4@gmail.com> (raw)
In-Reply-To: <20210712000322.4224-6-digetx@gmail.com>
12.07.2021 03:03, Dmitry Osipenko пишет:
> Enable compile testing of tegra-cpuidle driver.
>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
> drivers/cpuidle/Kconfig.arm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpuidle/Kconfig.arm b/drivers/cpuidle/Kconfig.arm
> index 334f83e56120..599286fc0b08 100644
> --- a/drivers/cpuidle/Kconfig.arm
> +++ b/drivers/cpuidle/Kconfig.arm
> @@ -99,7 +99,7 @@ config ARM_MVEBU_V7_CPUIDLE
>
> config ARM_TEGRA_CPUIDLE
> bool "CPU Idle Driver for NVIDIA Tegra SoCs"
> - depends on ARCH_TEGRA && !ARM64
> + depends on (ARCH_TEGRA || COMPILE_TEST) && !ARM64 && MMU
> select ARCH_NEEDS_CPU_IDLE_COUPLED if SMP
> select ARM_CPU_SUSPEND
> help
>
Daniel, could you please ack this patch?
prev parent reply other threads:[~2021-08-16 15:32 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 ` [PATCH v2 4/5] clk: tegra: Add stubs needed " Dmitry Osipenko
2021-07-12 0:03 ` [PATCH v2 5/5] cpuidle: tegra: Enable " Dmitry Osipenko
2021-08-16 15:32 ` Dmitry Osipenko [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=bae8fc99-b29e-0721-c37e-a29898c7cba4@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).