From: Michael Walle <michael@walle.cc>
To: Randolph Sapp <rs@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
vigneshr@ti.com, kristo@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, d-gole@ti.com,
afd@ti.com, bb@ti.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
detheridge@ti.com, matt.coster@imgtec.com
Subject: Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64
Date: Tue, 19 Aug 2025 08:38:43 +0200 [thread overview]
Message-ID: <f0353dea24751f2f2ad6e7735232b933@walle.cc> (raw)
In-Reply-To: <DC5T752T3P8B.1UC57G2GH35Z5@ti.com>
Hi,
>> Apart from that, we now have two series which partly overlap.
>> Should I repost mine, as that's more than just the DT entry? (Which
>> doesn't work as is, I'd guess.)
>
> Ah, I don't see that series on the linux-arm-kernel list. If you can
> forward me
> that I can work around whatever you've got.
That was the one Nishanth mentioned earlier:
https://lore.kernel.org/linux-arm-kernel/20250716134717.4085567-1-mwalle@kernel.org/
Also this:
https://lore.kernel.org/all/DC5KCSEUZQUJ.3KPENNUQBUFM8@kernel.org/
-michael
next prev parent reply other threads:[~2025-08-19 7:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 23:25 [PATCH 1/3] arm64: dts: ti: k3-am62p: Fix memory ranges for GPU rs
2025-08-08 23:25 ` [PATCH 2/3] arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64 rs
2025-08-13 15:17 ` Nishanth Menon
2025-08-13 17:56 ` Randolph Sapp
2025-08-13 18:10 ` Nishanth Menon
2025-08-13 18:42 ` Nishanth Menon
2025-08-14 20:40 ` Randolph Sapp
2025-08-15 1:16 ` Nishanth Menon
2025-08-08 23:25 ` [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: " rs
2025-08-13 15:18 ` Nishanth Menon
2025-08-13 17:58 ` Randolph Sapp
2025-08-13 18:13 ` Nishanth Menon
2025-08-18 6:22 ` Michael Walle
2025-08-18 19:43 ` Randolph Sapp
2025-08-19 6:38 ` Michael Walle [this message]
2025-08-19 20:47 ` Randolph Sapp
2025-08-21 11:33 ` Nishanth Menon
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=f0353dea24751f2f2ad6e7735232b933@walle.cc \
--to=michael@walle.cc \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=detheridge@ti.com \
--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=matt.coster@imgtec.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=rs@ti.com \
--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).