All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Andy Gross <agross@kernel.org>,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/8] pinctrl: qcom: fix indentation in Kconfig
Date: Fri, 2 Jun 2023 11:02:05 +0200	[thread overview]
Message-ID: <ea2c099b-7bfe-2056-00d8-b99fb24e6cf4@linaro.org> (raw)
In-Reply-To: <20230601152026.1182648-2-krzysztof.kozlowski@linaro.org>



On 1.06.2023 17:20, Krzysztof Kozlowski wrote:
> Use tab for correct Kconfig indentation.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>

Konrad
>  drivers/pinctrl/qcom/Kconfig | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/pinctrl/qcom/Kconfig b/drivers/pinctrl/qcom/Kconfig
> index 28b19458b20d..9f957d16cd68 100644
> --- a/drivers/pinctrl/qcom/Kconfig
> +++ b/drivers/pinctrl/qcom/Kconfig
> @@ -245,7 +245,7 @@ config PINCTRL_QCOM_SPMI_PMIC
>  	select PINMUX
>  	select PINCONF
>  	select GENERIC_PINCONF
> -  select GPIOLIB
> +	select GPIOLIB
>  	select GPIOLIB_IRQCHIP
>  	select IRQ_DOMAIN_HIERARCHY
>  	help
> @@ -260,7 +260,7 @@ config PINCTRL_QCOM_SSBI_PMIC
>  	select PINMUX
>  	select PINCONF
>  	select GENERIC_PINCONF
> -  select GPIOLIB
> +	select GPIOLIB
>  	select GPIOLIB_IRQCHIP
>  	select IRQ_DOMAIN_HIERARCHY
>  	help

  reply	other threads:[~2023-06-02  9:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 15:20 [PATCH 1/8] pinctrl: qcom: qdf2xxx: drop ACPI_PTR Krzysztof Kozlowski
2023-06-01 15:20 ` [PATCH 2/8] pinctrl: qcom: fix indentation in Kconfig Krzysztof Kozlowski
2023-06-02  9:02   ` Konrad Dybcio [this message]
2023-06-01 15:20 ` [PATCH 3/8] pinctrl: qcom: correct language typo (Technologies) Krzysztof Kozlowski
2023-06-02  9:02   ` Konrad Dybcio
2023-06-01 15:20 ` [PATCH 4/8] pinctrl: qcom: drop unneeded GPIOLIB dependency Krzysztof Kozlowski
2023-06-02  9:03   ` Konrad Dybcio
2023-06-01 15:20 ` [PATCH 5/8] pinctrl: qcom: mark true OF dependency - common MSM pinctrl code Krzysztof Kozlowski
2023-06-02  9:07   ` Konrad Dybcio
2023-06-01 15:20 ` [PATCH 6/8] pinctrl: qcom: allow true compile testing Krzysztof Kozlowski
2023-06-02  9:08   ` Konrad Dybcio
2023-06-02  9:17     ` Krzysztof Kozlowski
2023-06-02  9:08   ` Konrad Dybcio
2023-06-01 15:20 ` [PATCH 7/8] pinctrl: qcom: organize main SoC drivers in new Kconfig.msm Krzysztof Kozlowski
2023-06-01 21:45   ` andy.shevchenko
2023-06-02  7:47   ` Linus Walleij
2023-06-02  9:09   ` Konrad Dybcio
2023-06-01 15:20 ` [PATCH 8/8] pinctrl: qcom: organize audio drivers in menuconfig Krzysztof Kozlowski
2023-06-01 21:42 ` [PATCH 1/8] pinctrl: qcom: qdf2xxx: drop ACPI_PTR andy.shevchenko
2023-06-02  9:01 ` Konrad Dybcio
2023-06-09  7:12 ` Linus Walleij
2023-06-09 10:09   ` Krzysztof Kozlowski

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=ea2c099b-7bfe-2056-00d8-b99fb24e6cf4@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.