From: Marcel Ziswiler <marcel@ziswiler.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Abel Vesa <abel.vesa@nxp.com>, Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
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>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 12/12] clk: imx8mm: don't use multiple blank lines
Date: Thu, 21 Jul 2022 21:59:35 +0200 [thread overview]
Message-ID: <20220721195936.1082422-13-marcel@ziswiler.com> (raw)
In-Reply-To: <20220721195936.1082422-1-marcel@ziswiler.com>
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Avoid the following checkpatch warning:
include/dt-bindings/clock/imx8mm-clock.h:284: check: Please don't use
multiple blank lines
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
---
include/dt-bindings/clock/imx8mm-clock.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/dt-bindings/clock/imx8mm-clock.h b/include/dt-bindings/clock/imx8mm-clock.h
index 47c6f7f9582c..1f768b2eeb1a 100644
--- a/include/dt-bindings/clock/imx8mm-clock.h
+++ b/include/dt-bindings/clock/imx8mm-clock.h
@@ -281,7 +281,6 @@
#define IMX8MM_CLK_CLKOUT2_DIV 256
#define IMX8MM_CLK_CLKOUT2 257
-
#define IMX8MM_CLK_END 258
#endif
--
2.35.1
prev parent reply other threads:[~2022-07-21 20:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 19:59 [PATCH v1 00/12] ARM: arm64: dts/clk: imx8mm: indentation whitespace cleanup Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 01/12] ARM: dts: imx6-sabrelite: change to use SPDX identifiers Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 02/12] ARM: dts: imx6qdl-mba6: don't use multiple blank lines Marcel Ziswiler
2022-07-22 6:12 ` Alexander Stein
2022-07-21 19:59 ` [PATCH v1 03/12] ARM: dts: imx6qdl: phytec: no spaces at start of line, indent use tabs Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 04/12] ARM: dts: imx6qdl-sabre: change to use SPDX identifiers Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 05/12] ARM: dts: imx7d-pico: indent use tabs, no spaces at start of line Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 06/12] ARM: dts: vf610: no spaces in indent but tabs Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 07/12] ARM: dts: vf610-twr: indent use tabs, no spaces at start of line Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 08/12] ARM: dts: vf610: don't use multiple blank lines Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 09/12] arm64: dts: imx8mm-venice-gw72xx-0x: blank line at end of file Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 10/12] arm64: dts: imx8mp-verdin: don't use multiple blank lines Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 11/12] arm64: dts: mnt-reform2: " Marcel Ziswiler
2022-07-22 12:37 ` Lucas Stach
2022-07-21 19:59 ` Marcel Ziswiler [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=20220721195936.1082422-13-marcel@ziswiler.com \
--to=marcel@ziswiler.com \
--cc=abel.vesa@nxp.com \
--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=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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