The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Tomas Melin <tomas.melin@vaisala.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "arm64: zynqmp: Add an OP-TEE node to the device tree"
Date: Mon, 15 Dec 2025 17:10:42 +0100	[thread overview]
Message-ID: <7e82a871-0234-409a-8fd3-a548cbb789e8@amd.com> (raw)
In-Reply-To: <0435af95-a3bc-4ec7-b07b-bdec42f25c56@vaisala.com>



On 12/15/25 16:43, Tomas Melin wrote:
> Hi,
> 
> On 15/12/2025 17:21, Michal Simek wrote:
>> Hi,
>>
>> On 12/12/25 13:09, Tomas Melin wrote:
>>> Hi,
>>>
>>> Is there some more specific information I can provide regarding this patch?
>>
>> I am trying to identify U-Boot code (2026.01-rc4) which does what you have
>> described in the commit message but I can't find it out.
>> Can you please point me directly to file, line number where that described logic
>> is skipped?
> 
> Please check lib/optee/optee.c, in particular lines 128 ->
> Target dt being linux kernel devicetree where the reserved-memory nodes
> are automatically injected. When node is already there, it bails out early.

I don't really mind that's why applied.

Thanks,
Michal



  reply	other threads:[~2025-12-15 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25  7:53 [PATCH] Revert "arm64: zynqmp: Add an OP-TEE node to the device tree" Tomas Melin
2025-11-25 10:30 ` Michal Simek
2025-11-25 11:42   ` Tomas Melin
2025-12-12 12:09     ` Tomas Melin
2025-12-15 15:21       ` Michal Simek
2025-12-15 15:43         ` Tomas Melin
2025-12-15 16:10           ` Michal Simek [this message]
2025-12-16  7:00             ` Tomas Melin
2025-12-16  7:12               ` Michal Simek

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=7e82a871-0234-409a-8fd3-a548cbb789e8@amd.com \
    --to=michal.simek@amd.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tomas.melin@vaisala.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