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: Wed, 30 Apr 2025 14:55:34 +0530 [thread overview]
Message-ID: <0f6e01dbb9b1$d52519d0$7f6f4d70$@samsung.com> (raw)
In-Reply-To: <b00514f2-55ca-49f0-aefb-ec1e784545d6@kernel.org>
Hi Krzysztof
> -----Original Message-----
> From: Krzysztof Kozlowski <krzk@kernel.org>
> Sent: Tuesday, April 29, 2025 6:37 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 29/04/2025 11:29, Yashwant Varur wrote:
> >
> > Please follow DTS coding style carefully. This applies to all commits you try to
> send from your downstream/vendor code.
>
>
> hm?
>
Got the issue, coding style says
Node and property names can use only the following characters:
Lowercase characters: [a-z]
Digits: [0-9]
Dash: -
I was using underscore for node name.
> >>
> > 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.
>
> I don't understand what is your reply here and what is quote. Use standard email
> style, not some mySingle or Outlook output. I suggest reading typical guidelines
> how to use email based workflows (kernel also has one).
>
Looks like mailer was not configured properly, hope this time it is fine.
I am working on upstreaming Ethernet driver for exynosauto (which has a variant of STMMAC controller)
What I wanted to reply previously was, will add pin control, along with Ethernet node(which will consume the pincontrol) and
I realize that first dt-binding should go for this IP.
My plan is to send Ethernet driver along with Ethernet dtsi node as well.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-04-30 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250423060042epcas5p2c04be779e21089f33b8a9a7785bb151a@epcas5p2.samsung.com>
2025-04-23 6:00 ` [PATCH] arm64: dts: exynos: Added the ethernet pin configuration 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
2025-04-29 13:07 ` Krzysztof Kozlowski
2025-04-30 9:25 ` Yashwant Varur [this message]
2025-05-02 22:37 kernel test robot
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='0f6e01dbb9b1$d52519d0$7f6f4d70$@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 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.