From: Frank.Li@oss.nxp.com
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: Frank Li <Frank.Li@nxp.com>,
vladimir.oltean@nxp.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux@ew.tq-group.com
Subject: Re: [PATCH v3 00/11] arm64: dts: describe the Lynx 10G and 28G SerDes blocks for Layerscape SoCs
Date: Mon, 27 Jul 2026 12:22:38 -0400 [thread overview]
Message-ID: <178516930294.2511550.7471897073188886058.b4-ty@b4> (raw)
In-Reply-To: <20260717120635.2118610-1-ioana.ciornei@nxp.com>
From: Frank Li <Frank.Li@nxp.com>
On Fri, 17 Jul 2026 15:06:24 +0300, Ioana Ciornei wrote:
> This patch set adds the device tree nodes for the Lynx10G SerDes blocks
> found on the LS1028A, LS1046A, LS1088A and LS2088A SoCs.
>
> The first 5 patches slowly change the LX2160A DTS support to a new
> structure which does not use any delete-node or delete-property
> directives. This is a direct result of the discussion with Frank in the
> v2 of this set:
> https://lore.kernel.org/all/akwAmzAbtg0Ejey0@SMW015318/
>
> [...]
Applied, thanks!
[01/11] arm64: dts: lx2160a: explicitly enable serdes_1 node
commit: 8f62ead195283b8620070985ae642a5a1db88843
[02/11] arm64: dts: lx2160a: extract the PCIe nodes into a separate dtsi
commit: 12422fe9b3f4876f953bb1699e8c2c18084e58d9
[03/11] arm64: dts: lx2160a: extract the SerDes nodes into a separate dtsi
commit: 9f0f43baf1ed556e6b16ddd5403dc44c5f21eb6a
[04/11] arm64: dts: lx2160a: extract the PCIe from LX2160A Rev2 into a separate file
commit: 8f69555ef54c59aa0207cdd0e15939417730a4e4
[05/11] arm64: dts: lx2160a: split the dtsi to avoid delete-property
commit: 285560f0d39dd6cd40c5c83470e4d3e43effd4b8
[06/11] arm64: dts: lx2160a: transition to device-specific SerDes compatible strings
commit: bc12e3ee01c82f2da45c6240b74f501b82732b27
[07/11] arm64: dts: lx2162a: transition to device-specific SerDes compatible strings
commit: 21cb12ad026e91aca65329531554ec1e74a32e77
[08/11] arm64: dts: ls1028a: describe the Lynx 10G SerDes
commit: 2b64e802a7c8a577616289b023a98e009318123d
[09/11] arm64: dts: ls1046a: describe the Lynx 10G SerDes blocks
commit: 65121d706ecd9c7b1365f91cc9f4e3c01fd9f15b
[10/11] arm64: dts: ls208xa: describe the Lynx 10G SerDes blocks
commit: 9eb4d238348fb1b81cc25ec3c50c13b85b6055d1
[11/11] arm64: dts: ls1088a: describe the Lynx 10G SerDes blocks
commit: c482d6c37187fe38662f278213301b7828cda662
Remove "This patch" and "we ..." in commit message
Best regards,
--
Frank Li <Frank.Li@nxp.com>
prev parent reply other threads:[~2026-07-27 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 12:06 [PATCH v3 00/11] arm64: dts: describe the Lynx 10G and 28G SerDes blocks for Layerscape SoCs Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 01/11] arm64: dts: lx2160a: explicitly enable serdes_1 node Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 02/11] arm64: dts: lx2160a: extract the PCIe nodes into a separate dtsi Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 03/11] arm64: dts: lx2160a: extract the SerDes " Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 04/11] arm64: dts: lx2160a: extract the PCIe from LX2160A Rev2 into a separate file Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 05/11] arm64: dts: lx2160a: split the dtsi to avoid delete-property Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 06/11] arm64: dts: lx2160a: transition to device-specific SerDes compatible strings Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 07/11] arm64: dts: lx2162a: " Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 08/11] arm64: dts: ls1028a: describe the Lynx 10G SerDes Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 09/11] arm64: dts: ls1046a: describe the Lynx 10G SerDes blocks Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 10/11] arm64: dts: ls208xa: " Ioana Ciornei
2026-07-17 12:06 ` [PATCH v3 11/11] arm64: dts: ls1088a: " Ioana Ciornei
2026-07-17 15:53 ` [PATCH v3 00/11] arm64: dts: describe the Lynx 10G and 28G SerDes blocks for Layerscape SoCs Frank Li
2026-07-27 16:22 ` Frank.Li [this message]
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=178516930294.2511550.7471897073188886058.b4-ty@b4 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=ioana.ciornei@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=robh@kernel.org \
--cc=vladimir.oltean@nxp.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