From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Marco Felsch <m.felsch@pengutronix.de>
Subject: Re: [PATCH] ARM: atf: document BL32 FDT argument
Date: Tue, 28 Oct 2025 09:28:24 +0100 [thread overview]
Message-ID: <176164010436.2805600.3285829784252912413.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20251024164133.1937633-1-m.felsch@pengutronix.de>
On Fri, 24 Oct 2025 18:41:27 +0200, Marco Felsch wrote:
> Document the BL32 arg3 FDT passing to avoid confusions since OP-TEE
> expects the FDT via arg2 and not arg3. That the TF-A is shifting the
> arguments is not very obvious.
>
>
Applied, thanks!
[1/1] ARM: atf: document BL32 FDT argument
https://git.pengutronix.de/cgit/barebox/commit/?id=81e31075e426 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-10-28 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 16:41 Marco Felsch
2025-10-28 8:28 ` Sascha Hauer [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=176164010436.2805600.3285829784252912413.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@pengutronix.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