From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Andrew Halaney <ahalaney@redhat.com>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
"Tero Kristo" <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
Siddharth Vadapalli <s-vadapalli@ti.com>, <mranostay@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: ti: k3-j784s4-evm: Consolidate serdes0 references
Date: Thu, 11 Jul 2024 11:05:33 +0530 [thread overview]
Message-ID: <0569049b-89fc-4914-9f78-a2f0f4824c43@ti.com> (raw)
In-Reply-To: <20240710-k3-j784s4-evm-serdes0-cleanup-v1-2-03850fe33922@redhat.com>
On Wed, Jul 10, 2024 at 10:36:14AM -0500, Andrew Halaney wrote:
> Subnodes were added to serdes0 in two different spots (due to independent
> development of their consumer usage). Let's go ahead and combine those
> into one reference for readability's sake.
>
> Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
This patch could probably be squashed into the previous one.
Irrespective of that,
Reviewed-by: Siddharth Vadapalli <s-vadapalli@ti.com>
[...]
Regards,
Siddharth.
next prev parent reply other threads:[~2024-07-11 5:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 15:36 [PATCH 0/2] arm64: dts: ti: k3-j784s4-evm: SERDES0 lane cleanup Andrew Halaney
2024-07-10 15:36 ` [PATCH 1/2] arm64: dts: ti: k3-j784s4-evm: Assign only lanes 0 and 1 to PCIe1 Andrew Halaney
2024-07-11 5:32 ` Siddharth Vadapalli
2024-07-10 15:36 ` [PATCH 2/2] arm64: dts: ti: k3-j784s4-evm: Consolidate serdes0 references Andrew Halaney
2024-07-11 5:35 ` Siddharth Vadapalli [this message]
2024-10-28 15:05 ` [PATCH 0/2] arm64: dts: ti: k3-j784s4-evm: SERDES0 lane cleanup Vignesh Raghavendra
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=0569049b-89fc-4914-9f78-a2f0f4824c43@ti.com \
--to=s-vadapalli@ti.com \
--cc=ahalaney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mranostay@ti.com \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=vigneshr@ti.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).