From: Nathan Chancellor <nathan@kernel.org>
To: Kevin Hilman <khilman@baylibre.com>, Tony Lindgren <tony@atomide.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Schiffer <matthias.schiffer@tq-group.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
linux@ew.tq-group.com, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, llvm@lists.linux.dev,
patches@lists.linux.dev, Nathan Chancellor <nathan@kernel.org>
Subject: [PATCH v2] ARM: dts: omap: am335x-mba335x: Fix stray '/*' in comment
Date: Wed, 05 Nov 2025 13:41:09 -0700 [thread overview]
Message-ID: <20251105-omap-mba335x-fix-clang-comment-warning-v2-1-f8a0003e1003@kernel.org> (raw)
When preprocessing arch/arm/boot/dts/ti/omap/am335x-mba335x.dts with
clang, there are a couple of warnings about '/*' within a block comment.
arch/arm/boot/dts/ti/omap/am335x-mba335x.dts:260:7: warning: '/*' within block comment [-Wcomment]
260 | /* /* gpmc_csn3.gpio2_0 - interrupt */
| ^
arch/arm/boot/dts/ti/omap/am335x-mba335x.dts:267:7: warning: '/*' within block comment [-Wcomment]
267 | /* /* gpmc_ben1.gpio1_28 - interrupt */
| ^
Remove the duplicate '/*' to clear up the warning.
Fixes: 5267fcd180b1 ("ARM: dts: omap: Add support for TQMa335x/MBa335x")
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
---
Changes in v2:
- Fix subject (sorry for the quick update...)
- Link to v1: https://patch.msgid.link/20251105-omap-mba335x-fix-clang-comment-warning-v1-1-9b671ee2cb93@kernel.org
---
arch/arm/boot/dts/ti/omap/am335x-mba335x.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/ti/omap/am335x-mba335x.dts b/arch/arm/boot/dts/ti/omap/am335x-mba335x.dts
index e51a8a17e74c..f05e5a8c2d61 100644
--- a/arch/arm/boot/dts/ti/omap/am335x-mba335x.dts
+++ b/arch/arm/boot/dts/ti/omap/am335x-mba335x.dts
@@ -257,14 +257,14 @@ AM33XX_PADCONF(AM335X_PIN_MCASP0_AHCLKR, PIN_OUTPUT, MUX_MODE4)
expander1_pins: expander1-pins {
pinctrl-single,pins = <
- /* /* gpmc_csn3.gpio2_0 - interrupt */
+ /* gpmc_csn3.gpio2_0 - interrupt */
AM33XX_PADCONF(AM335X_PIN_GPMC_CSN3, PIN_INPUT_PULLUP, MUX_MODE7 )
>;
};
expander2_pins: expander2-pins {
pinctrl-single,pins = <
- /* /* gpmc_ben1.gpio1_28 - interrupt */
+ /* gpmc_ben1.gpio1_28 - interrupt */
AM33XX_PADCONF(AM335X_PIN_GPMC_BEN1, PIN_INPUT_PULLUP, MUX_MODE7)
>;
};
---
base-commit: 25e10e2c94da2c7d18d72bd32d60d26d0c29232e
change-id: 20251105-omap-mba335x-fix-clang-comment-warning-adeb847a03d7
Best regards,
--
Nathan Chancellor <nathan@kernel.org>
next reply other threads:[~2025-11-05 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 20:41 Nathan Chancellor [this message]
2025-11-06 0:40 ` [PATCH v2] ARM: dts: omap: am335x-mba335x: Fix stray '/*' in comment Kevin Hilman
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=20251105-omap-mba335x-fix-clang-comment-warning-v2-1-f8a0003e1003@kernel.org \
--to=nathan@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=llvm@lists.linux.dev \
--cc=matthias.schiffer@tq-group.com \
--cc=patches@lists.linux.dev \
--cc=robh@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).