From: Krzysztof Kozlowski <krzk@kernel.org>
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
Date: Tue, 29 Apr 2025 15:07:12 +0200 [thread overview]
Message-ID: <b00514f2-55ca-49f0-aefb-ec1e784545d6@kernel.org> (raw)
In-Reply-To: <0ed501dbb8e9$45aa96e0$d0ffc4a0$@samsung.com>
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?
>>
> 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).
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-29 14:13 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 ` [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 [this message]
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=b00514f2-55ca-49f0-aefb-ec1e784545d6@kernel.org \
--to=krzk@kernel.org \
--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=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 \
--cc=yashwant.v@samsung.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).