From: "Markus Schneider-Pargmann" <msp@baylibre.com>
To: <sashiko-reviews@lists.linux.dev>,
"Markus Schneider-Pargmann (TI)" <msp@baylibre.com>
Cc: <conor+dt@kernel.org>, <robh@kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v8 7/9] arm64: dts: ti: k3-am62a: Split r5f memory region
Date: Thu, 03 Sep 2026 16:55:13 +0200 [thread overview]
Message-ID: <DL5RNTPIARVY.10YJNQ9AH2DDR@baylibre.com> (raw)
In-Reply-To: <20260903125534.48D651F000E9@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
On Thu Sep 3, 2026 at 2:55 PM CEST, sashiko-bot wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
> - [Critical] ABI breakage causing monolithic firmware loads to fail.
> - [High] SPL memory allocator overwrites DM firmware due to missing bootph-pre-ram tags.
Both of these are not issues. The firmware load in uboot ignores the
devicetree.
Best
Markus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 289 bytes --]
next prev parent reply other threads:[~2026-09-03 14:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 12:39 [PATCH v8 0/9] arm64: dts: ti: Split wkup R5F memory region for IO+DDR resume Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 1/9] arm64: dts: ti: k3-am62a-phycore-som: Fix wkup R5F memory region size Markus Schneider-Pargmann (TI)
2026-09-03 14:52 ` Andrew Davis
2026-09-03 15:20 ` Bryan Brattlof
2026-09-03 12:39 ` [PATCH v8 2/9] arm64: dts: ti: k3-am62d2-evm: " Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 3/9] arm64: dts: ti: k3-am62a7-sk: " Markus Schneider-Pargmann (TI)
2026-09-03 15:34 ` Bryan Brattlof
2026-09-03 12:39 ` [PATCH v8 4/9] arm64: dts: ti: k3-am62p-verdin: " Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 5/9] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 6/9] arm64: dts: ti: var-som-am62p: " Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 7/9] arm64: dts: ti: k3-am62a: Split r5f memory region Markus Schneider-Pargmann (TI)
2026-09-03 12:55 ` sashiko-bot
2026-09-03 14:55 ` Markus Schneider-Pargmann [this message]
2026-09-03 12:39 ` [PATCH v8 8/9] arm64: dts: ti: k3-am62p: " Markus Schneider-Pargmann (TI)
2026-09-03 12:57 ` sashiko-bot
2026-09-04 7:35 ` Markus Schneider-Pargmann
2026-09-03 12:39 ` [PATCH v8 9/9] arm64: dts: ti: Add wkup R5F nodes to pre-ram bootphase Markus Schneider-Pargmann (TI)
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=DL5RNTPIARVY.10YJNQ9AH2DDR@baylibre.com \
--to=msp@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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