U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Paresh Bhagat <p-bhagat@ti.com>
Cc: u-boot@lists.denx.de, praneeth@ti.com, vigneshr@ti.com,
	u-kumar1@ti.com, msp@baylibre.com, v-singh1@ti.com,
	anshuld@ti.com, afd@ti.com, m-chawdhry@ti.com,
	joao.goncalves@toradex.com, bb@ti.com, n-francis@ti.com,
	sebin.francis@ti.com
Subject: Re: [PATCH v2 0/4] Add DM firmware reserved memory support
Date: Fri, 17 Jul 2026 10:16:52 -0600	[thread overview]
Message-ID: <20260717161652.GS749385@bill-the-cat> (raw)
In-Reply-To: <d14d9e3a-2969-41da-8ed5-4c9ec465bc15@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]

On Fri, Jul 17, 2026 at 12:11:21PM +0530, Paresh Bhagat wrote:
> Hi Tom,
> 
> On 17/07/26 04:55, Tom Rini wrote:
> > On Wed, 01 Jul 2026 13:20:17 +0530, Paresh Bhagat wrote:
> > 
> > > This series adds support for DM firmware reserved memory fixup in device
> > > tree for K3 SoCs that use separate DM firmware (K3_DM_FW enabled).
> > > 
> > > The series includes:
> > > 1. Fix for phandle corruption in FDT reserved memory fixup
> > > 2. Enable OF_SYSTEM_SETUP for AM62D2 to allow device tree fixups
> > > 3. Add Kconfig options for DM firmware reserved memory for other K3 SoCs
> > > 4. Add DM reserved memory fixup implementation
> > > 
> > > [...]
> > Applied to u-boot/main, thanks!
> 
> 
> If possible could we revert this patch?
> This series conflicts from one other series and needs changes in approach
> how to fixup the DM reserved memory region.
> If this is merged without the corresponding device tree changes to include
> "dm", there will be a new node with same region causing memory overlap.
> Please refer to this:
> https://lore.kernel.org/all/20260706064104.138000-1-p-bhagat@ti.com/

Sorry I had missed that, reverted. I will note that if you register with
patchwork you should be able to manage the status of your own patches at
least.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-07-17 16:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01  7:50 [PATCH v2 0/4] Add DM firmware reserved memory support Paresh Bhagat
2026-07-01  7:50 ` [PATCH v2 1/4] arm: mach-k3: Fix phandle corruption in fdt fixup Paresh Bhagat
2026-07-02 15:13   ` Andrew Davis
2026-07-08  4:02   ` Neha Malcom Francis
2026-07-01  7:50 ` [PATCH v2 2/4] arm: mach-k3: am62ax: Enable OF_SYSTEM_SETUP for AM62D2 Paresh Bhagat
2026-07-01  7:50 ` [PATCH v2 3/4] arm: mack-k3: Kconfig: Add DM firmware reserved memory configs Paresh Bhagat
2026-07-02 18:12   ` Andrew Davis
2026-07-02 19:08     ` Francesco Dolcini
2026-07-01  7:50 ` [PATCH v2 4/4] arm: mach-k3: Add DM reserved memory fixup Paresh Bhagat
2026-07-08  4:02   ` Neha Malcom Francis
2026-07-06  6:41 ` [PATCH v2 0/4] Add DM firmware reserved memory support Paresh Bhagat
2026-07-16 23:25 ` Tom Rini
2026-07-17  6:41   ` Paresh Bhagat
2026-07-17 16:16     ` Tom Rini [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=20260717161652.GS749385@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=afd@ti.com \
    --cc=anshuld@ti.com \
    --cc=bb@ti.com \
    --cc=joao.goncalves@toradex.com \
    --cc=m-chawdhry@ti.com \
    --cc=msp@baylibre.com \
    --cc=n-francis@ti.com \
    --cc=p-bhagat@ti.com \
    --cc=praneeth@ti.com \
    --cc=sebin.francis@ti.com \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    --cc=v-singh1@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