From: Tom Rini <trini@konsulko.com>
To: Anshul Dalal <anshuld@ti.com>
Cc: u-boot@lists.denx.de, upstream@lists.phytec.de,
Nishanth Menon <nm@ti.com>,
Robert Nelson <robertcnelson@gmail.com>,
Wadim Egorov <w.egorov@phytec.de>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Garrett Giordano <ggiordano@phytec.com>,
Manorit Chawdhry <m-chawdhry@ti.com>, Bryan Brattlof <bb@ti.com>,
Paresh Bhagat <p-bhagat@ti.com>,
Vitor Soares <vitor.soares@toradex.com>,
Parth Pancholi <parth.pancholi@toradex.com>,
Andrew Davis <afd@ti.com>, Gowtham Tammana <g-tammana@ti.com>,
Vignesh R <vigneshr@ti.com>
Subject: Re: [PATCH master] arch: arm: dts: k3: refactor common nodes to k3-*-r5.dtsi
Date: Mon, 2 Feb 2026 08:38:11 -0600 [thread overview]
Message-ID: <20260202143811.GC2603314@bill-the-cat> (raw)
In-Reply-To: <DG4BZ97UWPF0.FCYZ7RUNHS94@ti.com>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
On Mon, Feb 02, 2026 at 01:55:19PM +0530, Anshul Dalal wrote:
> On Thu Jan 22, 2026 at 7:38 PM IST, Anshul Dalal wrote:
> > This patch refactors the nodes in each board's R5 device-tree to common
> > SoC level dtsi. No functional change is intended from this patch.
> >
> > Signed-off-by: Anshul Dalal <anshuld@ti.com>
>
> Any updates on this patch?
I've been letting it collect tags as it's not been quite 2 weeks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-02-02 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 14:08 [PATCH master] arch: arm: dts: k3: refactor common nodes to k3-*-r5.dtsi Anshul Dalal
2026-01-22 14:44 ` Francesco Dolcini
2026-01-22 14:48 ` Francesco Dolcini
2026-02-02 8:25 ` Anshul Dalal
2026-02-02 14:38 ` Tom Rini [this message]
2026-02-03 6:51 ` Wadim Egorov
2026-02-03 13:39 ` Bryan Brattlof
2026-02-06 8:23 ` Anshul Dalal
2026-02-06 13:47 ` Bryan Brattlof
2026-02-06 15:18 ` Bryan Brattlof
2026-02-06 18:15 ` Tom Rini
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=20260202143811.GC2603314@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=anshuld@ti.com \
--cc=bb@ti.com \
--cc=francesco.dolcini@toradex.com \
--cc=g-tammana@ti.com \
--cc=ggiordano@phytec.com \
--cc=m-chawdhry@ti.com \
--cc=nm@ti.com \
--cc=p-bhagat@ti.com \
--cc=parth.pancholi@toradex.com \
--cc=robertcnelson@gmail.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=vigneshr@ti.com \
--cc=vitor.soares@toradex.com \
--cc=w.egorov@phytec.de \
/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