netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Swathi K S <swathi.ks@samsung.com>,
	krzk+dt@kernel.org, linux-fsd@tesla.com, robh@kernel.org,
	conor+dt@kernel.org, richardcochran@gmail.com,
	alim.akhtar@samsung.com
Cc: jayati.sahu@samsung.com, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	pankaj.dubey@samsung.com, ravi.patel@samsung.com,
	gost.dev@samsung.com
Subject: Re: [PATCH v8 0/2] arm64: dts: fsd: Add Ethernet support for FSD SoC
Date: Fri, 28 Mar 2025 10:37:23 +0100	[thread overview]
Message-ID: <aad0e28d-1164-47fb-b08b-ee70d94eab9c@kernel.org> (raw)
In-Reply-To: <017801db9fbc$81bfa490$853eedb0$@samsung.com>

On 28/03/2025 09:36, Swathi K S wrote:
> 
> 
>> -----Original Message-----
>> From: Swathi K S <swathi.ks@samsung.com>
>> Sent: 18 March 2025 16:22
>> To: 'krzk+dt@kernel.org' <krzk+dt@kernel.org>; 'linux-fsd@tesla.com'
>> <linux-fsd@tesla.com>; 'robh@kernel.org' <robh@kernel.org>;
>> 'conor+dt@kernel.org' <conor+dt@kernel.org>; 'richardcochran@gmail.com'
>> <richardcochran@gmail.com>; 'alim.akhtar@samsung.com'
>> <alim.akhtar@samsung.com>
>> Cc: 'jayati.sahu@samsung.com' <jayati.sahu@samsung.com>; 'linux-arm-
>> kernel@lists.infradead.org' <linux-arm-kernel@lists.infradead.org>; 'linux-
>> samsung-soc@vger.kernel.org' <linux-samsung-soc@vger.kernel.org>;
>> 'devicetree@vger.kernel.org' <devicetree@vger.kernel.org>; 'linux-
>> kernel@vger.kernel.org' <linux-kernel@vger.kernel.org>;
>> 'netdev@vger.kernel.org' <netdev@vger.kernel.org>;
>> 'pankaj.dubey@samsung.com' <pankaj.dubey@samsung.com>;
>> 'ravi.patel@samsung.com' <ravi.patel@samsung.com>;
>> 'gost.dev@samsung.com' <gost.dev@samsung.com>
>> Subject: RE: [PATCH v8 0/2] arm64: dts: fsd: Add Ethernet support for FSD
>> SoC
>>
>>
>>
>>> -----Original Message-----
>>> From: Swathi K S <swathi.ks@samsung.com>
>>> Sent: 07 March 2025 10:19
>>> To: krzk+dt@kernel.org; linux-fsd@tesla.com; robh@kernel.org;
>>> conor+dt@kernel.org; richardcochran@gmail.com;
>>> alim.akhtar@samsung.com
>>> Cc: jayati.sahu@samsung.com; swathi.ks@samsung.com; linux-arm-
>>> kernel@lists.infradead.org; linux-samsung-soc@vger.kernel.org;
>>> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org;
>>> netdev@vger.kernel.org; pankaj.dubey@samsung.com;
>>> ravi.patel@samsung.com; gost.dev@samsung.com
>>> Subject: [PATCH v8 0/2] arm64: dts: fsd: Add Ethernet support for FSD
>>> SoC
>>>
>>> FSD platform has two instances of EQoS IP, one is in FSYS0 block and
>>> another one is in PERIC block. This patch series add required DT file
>>> modifications for the same.
>>>
>>> Changes since v1:
>>> 1. Addressed the format related corrections.
>>> 2. Addressed the MAC address correction.
>>>
>>> Changes since v2:
>>> 1. Corrected intendation issues.
>>>
>>> Changes since v3:
>>> 1. Removed alias names of ethernet nodes
>>>
>>> Changes since v4:
>>> 1. Added more details to the commit message as per review comment.
>>>
>>> Changes since v5:
>>> 1. Avoided inserting node in the end and inserted it in between as per
>>> address.
>>> 2. Changed the node label.
>>> 3. Separating DT patches from net patches and posting in different
>> branches.
>>>
>>> Changes since v6:
>>> 1. Addressed Andrew's review comment and removed phy-mode from
>> .dtsi
>>> to .dts
>>>
>>> Changes since v7:
>>> 1. Addressed Russell's review comment-Implemented clock tree setup in
>>> DT
>>>
>>
>> Hi,
>> The DT binding and driver patches corresponding to this patch is now
>> reflecting in linux-next
>> https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-
>> next.git/diff/Documentation/devicetree/bindings/net/tesla,fsd-
>> ethqos.yaml?id=f654ead4682a1d351d4d780b1b59ab02477b1185
>>
> 
> Hi reviewers, 
> Could you please confirm whether this set of patches can be considered for review or should I resend them?

Don't ping during merge window.

Best regards,
Krzysztof

  reply	other threads:[~2025-03-28  9:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250307045516epcas5p3b4006a5e2005beda04170179dc92ad16@epcas5p3.samsung.com>
2025-03-07  4:49 ` [PATCH v8 0/2] arm64: dts: fsd: Add Ethernet support for FSD SoC Swathi K S
2025-03-07  4:49   ` [PATCH v8 1/2] arm64: dts: fsd: Add Ethernet support for FSYS0 Block of " Swathi K S
2025-03-07  4:49   ` [PATCH v8 2/2] arm64: dts: fsd: Add Ethernet support for PERIC " Swathi K S
2025-03-18 10:52   ` [PATCH v8 0/2] arm64: dts: fsd: Add Ethernet support for " Swathi K S
2025-03-28  8:36   ` Swathi K S
2025-03-28  9:37     ` Krzysztof Kozlowski [this message]
2025-04-08 16:25   ` Krzysztof Kozlowski

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=aad0e28d-1164-47fb-b08b-ee70d94eab9c@kernel.org \
    --to=krzk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=jayati.sahu@samsung.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fsd@tesla.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pankaj.dubey@samsung.com \
    --cc=ravi.patel@samsung.com \
    --cc=richardcochran@gmail.com \
    --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).