From: Trevor Woerner <twoerner@gmail.com>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] ufs image class: add
Date: Sun, 15 Feb 2026 21:37:18 -0500 [thread overview]
Message-ID: <aZKC3qO6_iAKDWlB@localhost.localdomain> (raw)
In-Reply-To: <DGFOO2LV5U6R.2BRXDT44USDKP@bootlin.com>
Hello!
On Sun 2026-02-15 @ 05:41:17 PM, Mathieu Dubois-Briand wrote:
> On Fri Feb 13, 2026 at 5:36 PM CET, Trevor Woerner via lists.openembedded.org wrote:
> > Add an image class and wks file that demonstrates generating a wic image
> > with a 4096-byte sector size.
> >
> > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> > ---
>
> Thanks for your patch.
>
>
> > +
> > +IMAGE_CMD:wic.ufs () {
> > + out="${IMGDEPLOYDIR}/${IMAGE_NAME}"
>
> IMAGE_CMD:wic_ufs ?
>
> At least I believe this is the source of this warning:
>
> WARNING: core-image-minimal-1.0-r0 do_image_wic_ufs: Function do_image_wic_ufs doesn't exist
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/68/builds/3267
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/30/builds/3157
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/3210
Thank you for your report! I had not noticed this warning since it only
appears when wic.ufs is *not* requested (and since I was adding this
new IMAGE_FSTYPE it did not occur to me to test without it).
I thought my v2 had fixed the problem, but it didn't; please ignore.
But I believe my v3 found the problem and fixed it.
Thanks and best regards,
Trevor
prev parent reply other threads:[~2026-02-16 2:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 16:36 [PATCH 1/2] wic: re-implement sector-size support Trevor Woerner
2026-02-13 16:36 ` [PATCH 2/2] ufs image class: add Trevor Woerner
2026-02-15 16:41 ` [OE-core] " Mathieu Dubois-Briand
2026-02-16 2:37 ` Trevor Woerner [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=aZKC3qO6_iAKDWlB@localhost.localdomain \
--to=twoerner@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
/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