From: Zhihang Wei <wzh@ilbers.de>
To: srinuvasan.a@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH] meta-isar/recipes-initramfs: correct the initrd image name
Date: Thu, 27 Nov 2025 09:56:55 +0100 [thread overview]
Message-ID: <931d69a6-c862-476d-a305-f6d2f5595f57@ilbers.de> (raw)
In-Reply-To: <20251116111014.387091-1-srinuvasan.a@siemens.com>
Hi, I'll fix the issue INITRD_IMAGE and IMAGE_INITRD caused on CI first
and come back to this patch.
Zhihang
On 11/16/25 12:10, srinuvasan.a via isar-users wrote:
> From: Srinuvasan A <srinuvasan.a@siemens.com>
>
> The initrd image name was previously referenced as
> isar-initramfs-${DISTRO}-${MACHINE}.initrd.img,
> but no such file is generated under build/tmp/deploy/images/${MACHINE}
>
> Update the correct initrd image name in the comment sections
> of both the isar-initramfs and isar-dracut recipes.
>
> Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
> ---
> meta-isar/recipes-initramfs/images/isar-dracut.bb | 2 +-
> meta-isar/recipes-initramfs/images/isar-initramfs.bb | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta-isar/recipes-initramfs/images/isar-dracut.bb b/meta-isar/recipes-initramfs/images/isar-dracut.bb
> index aa55e360..efc4fc59 100644
> --- a/meta-isar/recipes-initramfs/images/isar-dracut.bb
> +++ b/meta-isar/recipes-initramfs/images/isar-dracut.bb
> @@ -1,6 +1,6 @@
> # Example of a custom initramfs image recipe. The image will be deployed to
> #
> -# build/tmp/deploy/images/${MACHINE}/isar-initramfs-${DISTRO}-${MACHINE}.initrd.img
> +# build/tmp/deploy/images/${MACHINE}/${IMAGE_FULLNAME}.initrd.img
> #
> # This software is a part of ISAR.
>
> diff --git a/meta-isar/recipes-initramfs/images/isar-initramfs.bb b/meta-isar/recipes-initramfs/images/isar-initramfs.bb
> index d2a946f7..9cadb96d 100644
> --- a/meta-isar/recipes-initramfs/images/isar-initramfs.bb
> +++ b/meta-isar/recipes-initramfs/images/isar-initramfs.bb
> @@ -1,6 +1,6 @@
> # Example of a custom initramfs image recipe. The image will be deployed to
> #
> -# build/tmp/deploy/images/${MACHINE}/isar-initramfs-${DISTRO}-${MACHINE}.initrd.img
> +# build/tmp/deploy/images/${MACHINE}/${IMAGE_FULLNAME}.initrd.img
> #
> # This software is a part of ISAR.
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/931d69a6-c862-476d-a305-f6d2f5595f57%40ilbers.de.
prev parent reply other threads:[~2025-11-27 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-16 11:10 srinuvasan.a via isar-users
2025-11-27 8:56 ` Zhihang Wei [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=931d69a6-c862-476d-a305-f6d2f5595f57@ilbers.de \
--to=wzh@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=srinuvasan.a@siemens.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