From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Philip Molloy <philip@philipmolloy.com>
Cc: buildroot@buildroot.org, Philip Molloy <philip.molloy@analog.com>,
Michael Hennerich <michael.hennerich@analog.com>
Subject: Re: [Buildroot] [PATCH 2/4] boot/uboot: depend on adsp-ldr if needed
Date: Mon, 18 Aug 2025 18:32:13 +0200 [thread overview]
Message-ID: <20250818183213.7cfd72bb@windsurf> (raw)
In-Reply-To: <20250818142203.421300-3-philip@philipmolloy.com>
Hello Philip,
On Mon, 18 Aug 2025 14:22:39 +0000
Philip Molloy <philip@philipmolloy.com> wrote:
> From: Philip Molloy <philip.molloy@analog.com>
>
> Signed-off-by: Philip Molloy <philip.molloy@analog.com>
> Signed-off-by: Philip Molloy <philip@philipmolloy.com>
Considering your PATCH 3/4, I don't think this patch is needed. Indeed,
PATCH 3/4 can simply add host-adsp-ldr in the dependencies of U-Boot
when BR2_TARGET_UBOOT_FORMAT_ADSP_LDR=y.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-18 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 14:22 [Buildroot] [PATCH 0/4] Generate ADI ADSP boot streams Philip Molloy
2025-08-18 14:22 ` [Buildroot] [PATCH 1/4] package/adsp-ldr: new package Philip Molloy
2025-08-18 16:31 ` Thomas Petazzoni via buildroot
2025-08-18 14:22 ` [Buildroot] [PATCH 2/4] boot/uboot: depend on adsp-ldr if needed Philip Molloy
2025-08-18 16:32 ` Thomas Petazzoni via buildroot [this message]
2025-08-18 14:22 ` [Buildroot] [PATCH 3/4] boot/uboot: add ADSP LDR binary format Philip Molloy
2025-08-18 14:22 ` [Buildroot] [PATCH 4/4] DEVELOPERS: add Philip Molloy for adsp-ldr Philip Molloy
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=20250818183213.7cfd72bb@windsurf \
--to=buildroot@buildroot.org \
--cc=michael.hennerich@analog.com \
--cc=philip.molloy@analog.com \
--cc=philip@philipmolloy.com \
--cc=thomas.petazzoni@bootlin.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