From: "Yashwant Varur" <yashwant.v@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<alim.akhtar@samsung.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <cs0617.lee@samsung.com>, <g.naidu@samsung.com>,
<niyas.ahmed@samsung.com>
Subject: RE: [PATCH] arm64: dts: exynos: Added the ethernet pin configuration
Date: Tue, 29 Apr 2025 14:59:54 +0530 [thread overview]
Message-ID: <0ed501dbb8e9$45aa96e0$d0ffc4a0$@samsung.com> (raw)
In-Reply-To: <73a5d0a6-ceb0-4c47-9992-260828f074d0@kernel.org>
-----Original Message-----
From: Krzysztof Kozlowski <krzk@kernel.org>
Sent: Wednesday, April 23, 2025 8:41 PM
To: Yashwant Varur <yashwant.v@samsung.com>; robh@kernel.org; krzk+dt@kernel.org; conor+dt@kernel.org; alim.akhtar@samsung.com; devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-samsung-soc@vger.kernel.org; linux-kernel@vger.kernel.org
Cc: cs0617.lee@samsung.com; g.naidu@samsung.com; niyas.ahmed@samsung.com
Subject: Re: [PATCH] arm64: dts: exynos: Added the ethernet pin configuration
On 23/04/2025 08:00, Yashwant Varur wrote:
> This patch adds the ethernet pin configuration.
>
> Signed-off-by: Yashwant Varur <yashwant.v@samsung.com>
> Signed-off-by: Changsub Lee <cs0617.lee@samsung.com>
Incorrect chain or confusing. Who was the author? What is the meaning of the last SoB?
>
Sorry will correct the order.
> ---
> .../dts/exynos/exynosautov920-pinctrl.dtsi | 41 +++++++++++++++++++
> 1 file changed, 41 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/exynos/exynosautov920-pinctrl.dtsi
> b/arch/arm64/boot/dts/exynos/exynosautov920-pinctrl.dtsi
> index 663e8265cbf5..778584d339d5 100644
> --- a/arch/arm64/boot/dts/exynos/exynosautov920-pinctrl.dtsi
> +++ b/arch/arm64/boot/dts/exynos/exynosautov920-pinctrl.dtsi
> @@ -166,6 +166,24 @@ gph6: gph6-gpio-bank {
> interrupt-controller;
> #interrupt-cells = <2>;
> };
> +
> + eth0_pps_out: eth0_pps_out {
Please follow DTS coding style carefully. This applies to all commits you try to send from your downstream/vendor code.
>
Sure, thanks
What is more important, I don't really understand why you are doing this
- there is no user of these entries - and commit msg does not help here.
>
Understood, in v2 will add the Ethernet node as well.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-29 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250423060042epcas5p2c04be779e21089f33b8a9a7785bb151a@epcas5p2.samsung.com>
2025-04-23 6:00 ` Yashwant Varur
2025-04-23 8:23 ` Alim Akhtar
2025-04-23 13:37 ` Rob Herring (Arm)
2025-04-23 15:11 ` Krzysztof Kozlowski
2025-04-29 9:29 ` Yashwant Varur [this message]
2025-04-29 13:07 ` Krzysztof Kozlowski
2025-04-30 9:25 ` Yashwant Varur
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='0ed501dbb8e9$45aa96e0$d0ffc4a0$@samsung.com' \
--to=yashwant.v@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=cs0617.lee@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=g.naidu@samsung.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=niyas.ahmed@samsung.com \
--cc=robh@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
all inboxes | Powered by JetHome®