From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Anton Mikanovich <amikan@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] initramfs: Align custom built image name to standard one
Date: Mon, 15 Dec 2025 13:23:56 +0100 [thread overview]
Message-ID: <fa4d20df-2206-43be-810e-ef9663405460@siemens.com> (raw)
In-Reply-To: <e0d1e3d5-3152-4dec-a302-9c98c4bd1c48@ilbers.de>
On 15.12.25 13:14, Anton Mikanovich wrote:
> 12/12/2025 21:58, 'Jan Kiszka' via isar-users wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> As now both standard initramfs as well as custom ones define their
>> deployment name via INITRD_DEPLOY_FILE, they also need to use the same
>> naming pattern, or things are falling apart, e.g. in downstream layers
>> that actually use INITRAMFS_IMAGE_NAME as image name source.
>>
>> Update the testsuite as well, even in places where the image name is
>> self-defined, just to avoid confusion.
>>
>> Fixes: c3c4e72cbfc4 ("image: introduce IMAGE_INITRD, deprecate
>> INITRD_IMAGE")
>> Fixes: 8dbffe075b15 ("RECIPE-API-CHANGELOG: Fix entry for IMAGE_INITRD")
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>
> Hello Jan,
>
> Thanks for the fix, we've just introduced new "Priority Review" state in
> Patchwork, so anyone can check the state of hotfix patches anytime.
>
> See: https://patchwork.isar-build.org/project/isar/patch/0f4b40c6-
> ee79-4209-9150-59b902670510@siemens.com/
>
> To all: As this marking is doing manually, feel free to inform if any
> commit
> should be also marked.
>
Ah, that's nice!
Do you happen to know if patchwork also supports some kind of
notifications? My account on patchwork.kernel.org talks about that in
the profile settings, but that may only apply to maintainers, and it
likely also needs an account on the platform.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
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/fa4d20df-2206-43be-810e-ef9663405460%40siemens.com.
next prev parent reply other threads:[~2025-12-15 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 19:58 'Jan Kiszka' via isar-users
2025-12-15 12:14 ` Anton Mikanovich
2025-12-15 12:23 ` 'Jan Kiszka' via isar-users [this message]
2025-12-16 9:07 ` Anton Mikanovich
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=fa4d20df-2206-43be-810e-ef9663405460@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=jan.kiszka@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