From: Rob Herring <robh@kernel.org>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Nishanth Menon <nm@ti.com>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 3/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62
Date: Fri, 11 Feb 2022 10:41:16 -0600 [thread overview]
Message-ID: <YgaRrBVMP/Jv67cs@robh.at.kernel.org> (raw)
In-Reply-To: <20220208131827.1430086-4-vigneshr@ti.com>
On Tue, 08 Feb 2022 18:48:25 +0530, Vignesh Raghavendra wrote:
> From: Suman Anna <s-anna@ti.com>
>
> Add pinctrl macros for AM62x SoCs. These macro definitions are similar
> to that of previous platforms, but adding new definitions to avoid any
> naming confusions in the SoC dts files.
>
> checkpatch insists the following error exists:
> ERROR: Macros with complex values should be enclosed in parentheses
>
> However, we do not need parentheses enclosing the values for this
> macro as we do intend it to generate two separate values as has been
> done for other similar platforms.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> ---
> include/dt-bindings/pinctrl/k3.h | 3 +++
> 1 file changed, 3 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Nishanth Menon <nm@ti.com>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 3/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62
Date: Fri, 11 Feb 2022 10:41:16 -0600 [thread overview]
Message-ID: <YgaRrBVMP/Jv67cs@robh.at.kernel.org> (raw)
In-Reply-To: <20220208131827.1430086-4-vigneshr@ti.com>
On Tue, 08 Feb 2022 18:48:25 +0530, Vignesh Raghavendra wrote:
> From: Suman Anna <s-anna@ti.com>
>
> Add pinctrl macros for AM62x SoCs. These macro definitions are similar
> to that of previous platforms, but adding new definitions to avoid any
> naming confusions in the SoC dts files.
>
> checkpatch insists the following error exists:
> ERROR: Macros with complex values should be enclosed in parentheses
>
> However, we do not need parentheses enclosing the values for this
> macro as we do intend it to generate two separate values as has been
> done for other similar platforms.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> ---
> include/dt-bindings/pinctrl/k3.h | 3 +++
> 1 file changed, 3 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-11 16:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 13:18 [PATCH 0/5] arm64: Initial support for Texas Instruments AM62 Platform Vignesh Raghavendra
2022-02-08 13:18 ` Vignesh Raghavendra
2022-02-08 13:18 ` [PATCH 1/5] soc: ti: k3-socinfo: Add AM62x JTAG ID Vignesh Raghavendra
2022-02-08 13:18 ` Vignesh Raghavendra
2022-02-08 13:18 ` [PATCH 2/5] dt-bindings: arm: ti: Add bindings for AM625 SoC Vignesh Raghavendra
2022-02-08 13:18 ` Vignesh Raghavendra
2022-02-08 17:01 ` Krzysztof Kozlowski
2022-02-08 17:01 ` Krzysztof Kozlowski
2022-02-09 19:04 ` Vignesh Raghavendra
2022-02-09 19:04 ` Vignesh Raghavendra
2022-02-09 21:29 ` Krzysztof Kozlowski
2022-02-09 21:29 ` Krzysztof Kozlowski
2022-02-11 16:39 ` Rob Herring
2022-02-11 16:39 ` Rob Herring
2022-02-08 13:18 ` [PATCH 3/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62 Vignesh Raghavendra
2022-02-08 13:18 ` Vignesh Raghavendra
2022-02-11 16:41 ` Rob Herring [this message]
2022-02-11 16:41 ` Rob Herring
2022-02-08 13:18 ` [PATCH 4/5] arm64: dts: ti: Introduce base support for AM62x SoC Vignesh Raghavendra
2022-02-08 13:18 ` Vignesh Raghavendra
2022-02-08 17:05 ` Krzysztof Kozlowski
2022-02-08 17:05 ` Krzysztof Kozlowski
2022-02-09 19:04 ` Vignesh Raghavendra
2022-02-09 19:04 ` Vignesh Raghavendra
2022-02-09 21:36 ` Krzysztof Kozlowski
2022-02-09 21:36 ` Krzysztof Kozlowski
2022-02-09 19:10 ` Marc Zyngier
2022-02-09 19:10 ` Marc Zyngier
2022-02-10 19:34 ` Nishanth Menon
2022-02-10 19:34 ` Nishanth Menon
2022-02-11 11:33 ` Marc Zyngier
2022-02-11 11:33 ` Marc Zyngier
2022-02-11 23:55 ` Nishanth Menon
2022-02-11 23:55 ` Nishanth Menon
2022-02-12 11:40 ` Marc Zyngier
2022-02-12 11:40 ` Marc Zyngier
2022-02-15 21:12 ` Nishanth Menon
2022-02-15 21:12 ` Nishanth Menon
2022-02-08 13:18 ` [PATCH 5/5] arm64: dts: ti: Add support for AM62-SK Vignesh Raghavendra
2022-02-08 13:18 ` Vignesh Raghavendra
2022-02-08 17:08 ` Krzysztof Kozlowski
2022-02-08 17:08 ` Krzysztof Kozlowski
2022-02-09 19:05 ` Vignesh Raghavendra
2022-02-09 19:05 ` Vignesh Raghavendra
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=YgaRrBVMP/Jv67cs@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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 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.