From: Anton Mikanovich <amikan@ilbers.de>
To: srinuvasan.a@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH] doc: replace IMAGE_TYPE with IMAGE_FSTYPES
Date: Tue, 30 Jun 2026 17:00:42 +0300 [thread overview]
Message-ID: <6728ec8b-cc1f-4477-adce-e26f5c282984@ilbers.de> (raw)
In-Reply-To: <20260630135447.174067-1-srinuvasan.a@siemens.com>
On 30/06/2026 15:54, srinuvasan.a via isar-users wrote:
> From: Srinuvasan A <srinuvasan.a@siemens.com>
>
> Update the documentation to use IMAGE_FSTYPES instead of IMAGE_TYPE.
> Also update image type names to match the current convention, where
> the `-img` suffix has been removed (for example, `wic-img` becomes `wic`)
>
> Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
> ---
> RECIPE-API-CHANGELOG.md | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
> index 5d2514c0..fc3ff440 100644
> --- a/RECIPE-API-CHANGELOG.md
> +++ b/RECIPE-API-CHANGELOG.md
> @@ -24,7 +24,7 @@ cross-building.
> ### wic image type, removal of manual wic invocation
>
> Images that are described by wic files are now generated during the build by
> -setting `IMAGE_TYPE = "wic-img"`. The manual invocation of wic after the
> +setting `IMAGE_FSTYPES = "wic"`. The manual invocation of wic after the
> bitbake run is no longer needed nor supported.
>
> ### Optional kernel installation
There were no such a variable (IMAGE_FSTYPES) in v0.6 which this line
was for.
Rejected.
--
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/6728ec8b-cc1f-4477-adce-e26f5c282984%40ilbers.de.
prev parent reply other threads:[~2026-06-30 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 13:54 srinuvasan.a via isar-users
2026-06-30 14:00 ` Anton Mikanovich [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=6728ec8b-cc1f-4477-adce-e26f5c282984@ilbers.de \
--to=amikan@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