From: Abel Vesa <abel.vesa@linaro.org>
To: Marcel Ziswiler <marcel@ziswiler.com>
Cc: linux-arm-kernel@lists.infradead.org,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Abel Vesa <abelvesa@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v1 2/2] dt-bindings: imx8ulp: clock: no spaces before tabs
Date: Sun, 29 Jan 2023 19:44:55 +0200 [thread overview]
Message-ID: <Y9awlwWhjoH77dM2@linaro.org> (raw)
In-Reply-To: <20230119085421.102804-3-marcel@ziswiler.com>
On 23-01-19 09:54:21, Marcel Ziswiler wrote:
> From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
> This fixes the following warnings:
>
> include/dt-bindings/clock/imx8ulp-clock.h:204: warning: please, no space
> before tabs
> include/dt-bindings/clock/imx8ulp-clock.h:215: warning: please, no space
> before tabs
>
> Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Applied both.
Thanks.
>
> ---
>
> include/dt-bindings/clock/imx8ulp-clock.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/dt-bindings/clock/imx8ulp-clock.h b/include/dt-bindings/clock/imx8ulp-clock.h
> index 953ecfe8ebcc..827404fadf5c 100644
> --- a/include/dt-bindings/clock/imx8ulp-clock.h
> +++ b/include/dt-bindings/clock/imx8ulp-clock.h
> @@ -201,7 +201,7 @@
> #define IMX8ULP_CLK_SAI7 2
> #define IMX8ULP_CLK_SPDIF 3
> #define IMX8ULP_CLK_ISI 4
> -#define IMX8ULP_CLK_CSI_REGS 5
> +#define IMX8ULP_CLK_CSI_REGS 5
> #define IMX8ULP_CLK_PCTLD 6
> #define IMX8ULP_CLK_CSI 7
> #define IMX8ULP_CLK_DSI 8
> @@ -212,7 +212,7 @@
> #define IMX8ULP_CLK_GPU2D 13
> #define IMX8ULP_CLK_GPU3D 14
> #define IMX8ULP_CLK_DC_NANO 15
> -#define IMX8ULP_CLK_CSI_CLK_UI 16
> +#define IMX8ULP_CLK_CSI_CLK_UI 16
> #define IMX8ULP_CLK_CSI_CLK_ESC 17
> #define IMX8ULP_CLK_RGPIOD 18
> #define IMX8ULP_CLK_DMA2_MP 19
> --
> 2.36.1
>
next prev parent reply other threads:[~2023-01-29 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 8:54 [RESEND PATCH v1 0/2] ARM: arm64: dts/clk: imx: indentation permission whitespace cleanup 2 Marcel Ziswiler
2023-01-19 8:54 ` [RESEND PATCH v1 1/2] clk: imx6sll: add proper spdx license identifier Marcel Ziswiler
2023-01-29 17:37 ` Abel Vesa
2023-01-19 8:54 ` [RESEND PATCH v1 2/2] dt-bindings: imx8ulp: clock: no spaces before tabs Marcel Ziswiler
2023-01-19 10:32 ` Krzysztof Kozlowski
2023-01-29 17:43 ` Abel Vesa
2023-01-29 17:44 ` Abel Vesa [this message]
2023-01-29 17:42 ` [RESEND PATCH v1 0/2] ARM: arm64: dts/clk: imx: indentation permission whitespace cleanup 2 Abel Vesa
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=Y9awlwWhjoH77dM2@linaro.org \
--to=abel.vesa@linaro.org \
--cc=abelvesa@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marcel@ziswiler.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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).