From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2] cpuidle: Fix Kconfig indentation
Date: Fri, 29 Nov 2019 12:28:43 +0100 [thread overview]
Message-ID: <1785480.d7BT1UD6kJ@kreacher> (raw)
In-Reply-To: <1574306352-29264-1-git-send-email-krzk@kernel.org>
On Thursday, November 21, 2019 4:19:12 AM CET Krzysztof Kozlowski wrote:
> Adjust indentation from spaces to tab (+optional two spaces) as in
> coding style with command like:
> $ sed -e 's/^ /\t/' -i */Kconfig
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
>
> Changes since v1:
> 1. Fix also 7-space and tab+1 space indentation issues.
> ---
> drivers/cpuidle/Kconfig | 16 ++++++++--------
> drivers/cpuidle/Kconfig.arm | 16 ++++++++--------
> 2 files changed, 16 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/cpuidle/Kconfig b/drivers/cpuidle/Kconfig
> index 88727b7c0d59..c0aeedd66f02 100644
> --- a/drivers/cpuidle/Kconfig
> +++ b/drivers/cpuidle/Kconfig
> @@ -16,7 +16,7 @@ config CPU_IDLE
> if CPU_IDLE
>
> config CPU_IDLE_MULTIPLE_DRIVERS
> - bool
> + bool
>
> config CPU_IDLE_GOV_LADDER
> bool "Ladder governor (for periodic timer tick)"
> @@ -63,13 +63,13 @@ source "drivers/cpuidle/Kconfig.powerpc"
> endmenu
>
> config HALTPOLL_CPUIDLE
> - tristate "Halt poll cpuidle driver"
> - depends on X86 && KVM_GUEST
> - default y
> - help
> - This option enables halt poll cpuidle driver, which allows to poll
> - before halting in the guest (more efficient than polling in the
> - host via halt_poll_ns for some scenarios).
> + tristate "Halt poll cpuidle driver"
> + depends on X86 && KVM_GUEST
> + default y
> + help
> + This option enables halt poll cpuidle driver, which allows to poll
> + before halting in the guest (more efficient than polling in the
> + host via halt_poll_ns for some scenarios).
>
> endif
>
> diff --git a/drivers/cpuidle/Kconfig.arm b/drivers/cpuidle/Kconfig.arm
> index d8530475493c..e91ab792d14d 100644
> --- a/drivers/cpuidle/Kconfig.arm
> +++ b/drivers/cpuidle/Kconfig.arm
> @@ -3,15 +3,15 @@
> # ARM CPU Idle drivers
> #
> config ARM_CPUIDLE
> - bool "Generic ARM/ARM64 CPU idle Driver"
> - select DT_IDLE_STATES
> + bool "Generic ARM/ARM64 CPU idle Driver"
> + select DT_IDLE_STATES
> select CPU_IDLE_MULTIPLE_DRIVERS
> - help
> - Select this to enable generic cpuidle driver for ARM.
> - It provides a generic idle driver whose idle states are configured
> - at run-time through DT nodes. The CPUidle suspend backend is
> - initialized by calling the CPU operations init idle hook
> - provided by architecture code.
> + help
> + Select this to enable generic cpuidle driver for ARM.
> + It provides a generic idle driver whose idle states are configured
> + at run-time through DT nodes. The CPUidle suspend backend is
> + initialized by calling the CPU operations init idle hook
> + provided by architecture code.
>
> config ARM_PSCI_CPUIDLE
> bool "PSCI CPU idle Driver"
>
Applied as 5.5 material, thanks!
prev parent reply other threads:[~2019-11-29 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 3:19 [PATCH v2] cpuidle: Fix Kconfig indentation Krzysztof Kozlowski
2019-11-29 11:28 ` Rafael J. Wysocki [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=1785480.d7BT1UD6kJ@kreacher \
--to=rjw@rjwysocki.net \
--cc=daniel.lezcano@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
/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).