From: Krzysztof Kozlowski <krzk@kernel.org>
To: Swathi K S <swathi.ks@samsung.com>,
krzk+dt@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh@kernel.org, conor+dt@kernel.org, richardcochran@gmail.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com
Cc: rmk+kernel@armlinux.org.uk, netdev@vger.kernel.org,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, pankaj.dubey@samsung.com,
ravi.patel@samsung.com, gost.dev@samsung.com
Subject: Re: [PATCH v8 1/2] dt-bindings: net: Add FSD EQoS device tree bindings
Date: Thu, 6 Mar 2025 08:14:56 +0100 [thread overview]
Message-ID: <789ecb2f-dddc-491b-b9f8-5fb89058fd1b@kernel.org> (raw)
In-Reply-To: <20250305091246.106626-2-swathi.ks@samsung.com>
On 05/03/2025 10:12, Swathi K S wrote:
> Add FSD Ethernet compatible in Synopsys dt-bindings document. Add FSD
> Ethernet YAML schema to enable the DT validation.
>
> Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> Signed-off-by: Ravi Patel <ravi.patel@samsung.com>
> Signed-off-by: Swathi K S <swathi.ks@samsung.com>
> ---
> .../devicetree/bindings/net/snps,dwmac.yaml | 5 +-
> .../bindings/net/tesla,fsd-ethqos.yaml | 118 ++++++++++++++++++
> 2 files changed, 121 insertions(+), 2 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/tesla,fsd-ethqos.yaml
>
I tried and did not see any differences, so point me exactly to any
difference in the binding (binding!) which would justify dropping review?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-06 8:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250305091845epcas5p1689eda3ba03572377997897271636cfd@epcas5p1.samsung.com>
2025-03-05 9:12 ` [PATCH v8 0/2] net: stmmac: dwc-qos: Add FSD EQoS support Swathi K S
2025-03-05 9:12 ` [PATCH v8 1/2] dt-bindings: net: Add FSD EQoS device tree bindings Swathi K S
2025-03-05 15:42 ` Krzysztof Kozlowski
2025-03-06 3:40 ` Swathi K S
2025-03-06 7:05 ` Krzysztof Kozlowski
2025-03-06 7:48 ` Swathi K S
2025-03-06 7:14 ` Krzysztof Kozlowski [this message]
2025-03-06 7:44 ` Swathi K S
2025-03-06 8:31 ` Krzysztof Kozlowski
2025-03-06 8:33 ` Krzysztof Kozlowski
2025-03-05 9:12 ` [PATCH v8 2/2] net: stmmac: dwc-qos: Add FSD EQoS support Swathi K S
2025-03-05 14:43 ` Russell King (Oracle)
2025-03-12 17:56 ` Russell King (Oracle)
2025-03-18 10:56 ` Swathi K S
2025-03-06 7:09 ` [PATCH v8 0/2] " Krzysztof Kozlowski
2025-03-06 7:45 ` Swathi K S
2025-03-06 23:40 ` patchwork-bot+netdevbpf
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=789ecb2f-dddc-491b-b9f8-5fb89058fd1b@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=gost.dev@samsung.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=richardcochran@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh@kernel.org \
--cc=swathi.ks@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).