From: Guenter Roeck <linux@roeck-us.net>
To: Brian Norris <briannorris@chromium.org>
Cc: Heiko Stuebner <heiko@sntech.de>, Arnd Bergmann <arnd@arndb.de>,
Robin Murphy <robin.murphy@arm.com>,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] soc: rockchip: Clean up Kconfig whitespace
Date: Tue, 26 Apr 2022 13:13:59 -0700 [thread overview]
Message-ID: <20220426201359.GH4093517@roeck-us.net> (raw)
In-Reply-To: <20220426014545.628100-1-briannorris@chromium.org>
On Mon, Apr 25, 2022 at 06:45:42PM -0700, Brian Norris wrote:
> There are spaces instead of tabs, and other inconsistent indentation.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
>
> (no changes since v2)
>
> Changes in v2:
> * New patch
>
> drivers/soc/rockchip/Kconfig | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/soc/rockchip/Kconfig b/drivers/soc/rockchip/Kconfig
> index 156ac0e0c8fe..aff2f7e95237 100644
> --- a/drivers/soc/rockchip/Kconfig
> +++ b/drivers/soc/rockchip/Kconfig
> @@ -23,23 +23,23 @@ config ROCKCHIP_IODOMAIN
> voltage supplied by the regulators.
>
> config ROCKCHIP_PM_DOMAINS
> - bool "Rockchip generic power domain"
> - depends on PM
> - select PM_GENERIC_DOMAINS
> - help
> - Say y here to enable power domain support.
> - In order to meet high performance and low power requirements, a power
> - management unit is designed or saving power when RK3288 in low power
> - mode. The RK3288 PMU is dedicated for managing the power of the whole chip.
> + bool "Rockchip generic power domain"
> + depends on PM
> + select PM_GENERIC_DOMAINS
> + help
> + Say y here to enable power domain support.
> + In order to meet high performance and low power requirements, a power
> + management unit is designed or saving power when RK3288 in low power
> + mode. The RK3288 PMU is dedicated for managing the power of the whole chip.
>
> - If unsure, say N.
> + If unsure, say N.
>
> config ROCKCHIP_DTPM
> tristate "Rockchip DTPM hierarchy"
> depends on DTPM && m
> help
> - Describe the hierarchy for the Dynamic Thermal Power
> - Management tree on this platform. That will create all the
> - power capping capable devices.
> + Describe the hierarchy for the Dynamic Thermal Power Management tree
> + on this platform. That will create all the power capping capable
> + devices.
>
> endif
> --
> 2.36.0.rc2.479.g8af0fa9b8e-goog
>
next prev parent reply other threads:[~2022-04-26 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 1:45 [PATCH v3 1/3] soc: rockchip: Clean up Kconfig whitespace Brian Norris
2022-04-26 1:45 ` [PATCH v3 2/3] soc: rockchip: power-domain: Replace dsb() with smb() Brian Norris
2022-04-26 20:14 ` Guenter Roeck
2022-04-26 23:55 ` Peter Geis
2022-04-27 0:25 ` Robin Murphy
2022-04-27 21:47 ` Brian Norris
2022-04-26 1:45 ` [PATCH v3 3/3] soc: rockchip: Fix compile-testing SoC drivers Brian Norris
2022-04-26 20:14 ` Guenter Roeck
2022-04-26 20:13 ` Guenter Roeck [this message]
2022-04-30 14:05 ` [PATCH v3 1/3] soc: rockchip: Clean up Kconfig whitespace Heiko Stuebner
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=20220426201359.GH4093517@roeck-us.net \
--to=linux@roeck-us.net \
--cc=arnd@arndb.de \
--cc=briannorris@chromium.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robin.murphy@arm.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