From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <vgharaee@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v3 0/6] Add multi-kernel FIT image support
Date: Thu, 05 Nov 2026 16:01:06 +0100 [thread overview]
Message-ID: <DMND8NCBAAIS.2WLJVJJ9MFLNE@bootlin.com> (raw)
In-Reply-To: <20261031162649.944625-1-vgharaee@gmail.com>
On Sat Oct 31, 2026 at 5:26 PM CET, Vahid Gharaee via openembedded-core wrote:
> From: Vahid Gharaee <vgharaee@gmail.com>
>
> This patch series extends FIT image generation to support
> multiple kernel images and custom configurations.
> It allows different kernels, such as standard and real-time
> kernels, to be included in a single FIT image and
> selected at boot time.
>
> Vahid Gharaee (6):
Hi Vahid,
Sorry, I've been a bit slow to reply: this is conflicting with the
"kernel-fit-image: drop the synthetic FIT_LOADABLE_* values" patch that
was merged a few days ago. Can you rebase on master and send a new
version please?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-11-05 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 16:26 [PATCH v3 0/6] Add multi-kernel FIT image support Vahid Gharaee
2026-10-31 16:26 ` [PATCH v3 1/6] oe.fitimage: Support multiple kernel nodes and configuration selection Vahid Gharaee
2026-10-31 16:26 ` [PATCH v3 2/6] oe.fitimage: add metadata for multiple kernels Vahid Gharaee
2026-10-31 16:26 ` [PATCH v3 3/6] oe.selftest: Add tests for multi-kernel FIT config Vahid Gharaee
2026-10-31 16:26 ` [PATCH v3 4/6] oe.fitimage: Add custom configurations and harden multi-kernel handling Vahid Gharaee
2026-10-31 16:26 ` [PATCH v3 5/6] oe.selftest: Improve FIT DTB alias validation Vahid Gharaee
2026-10-31 16:26 ` [PATCH v3 6/6] kernel-fit-image: preserve vendored DTB aliases for external overrides Vahid Gharaee
2026-11-05 15:01 ` Mathieu Dubois-Briand [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=DMND8NCBAAIS.2WLJVJJ9MFLNE@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=vgharaee@gmail.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