From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: "Pavel Löbl" <pavel@loebl.cz>
Cc: openembedded-core@lists.openembedded.org,
Michelle Lin <michelle.linto91@gmail.com>
Subject: Re: [PATCH] uki.bbclass: fix ukify arguments assembly
Date: Thu, 2 Apr 2026 10:52:11 +0300 [thread overview]
Message-ID: <ac4gK-MO4ZadNHHf@nuoska> (raw)
In-Reply-To: <20260402073331.2436504-1-pavel@loebl.cz>
Hi,
On Thu, Apr 02, 2026 at 09:33:15AM +0200, Pavel L�bl wrote:
> Missing space before --uname ukify option mangles the command line
> string when KERNEL_VERSION is set.
Thanks, this is a clear bug.
meta/lib/oeqa/selftest/cases/uki.py could be improved to cover this.
I would be interested to know if the kernel version autodetection
does not work since that is preferred by ukify.py and this KERNEL_VERSION
handling in uki.bbclass could be removed.
Reviewed-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Cheers,
-Mikko
> Signed-off-by: Pavel L�bl <pavel@loebl.cz>
> ---
> meta/classes-recipe/uki.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes-recipe/uki.bbclass b/meta/classes-recipe/uki.bbclass
> index 326697a06660..a89e92b77869 100644
> --- a/meta/classes-recipe/uki.bbclass
> +++ b/meta/classes-recipe/uki.bbclass
> @@ -140,7 +140,7 @@ python do_uki() {
> # not always needed, ukify can detect version from kernel binary
> kernel_version = d.getVar('KERNEL_VERSION')
> if kernel_version:
> - ukify_cmd += "--uname %s" % (kernel_version)
> + ukify_cmd += " --uname %s" % (kernel_version)
> else:
> bb.fatal("ERROR - UKI_KERNEL_FILENAME not set")
>
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-04-02 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 7:33 [PATCH] uki.bbclass: fix ukify arguments assembly Pavel Löbl
2026-04-02 7:52 ` Mikko Rapeli [this message]
2026-04-02 10:22 ` Pavel Löbl
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=ac4gK-MO4ZadNHHf@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=michelle.linto91@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pavel@loebl.cz \
/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