All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Yoann Congal <yoann.congal@smile.fr>,
	adrian.freihofer@gmail.com, "Freihofer,
	Adrian" <adrian.freihofer@siemens.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: Ryan Eatmon <reatmon@ti.com>
Subject: Re: [OE-core] [wrynose][PATCH] kernel-fit-image.bbclass: Do not include kernel property in DTBO config subnodes
Date: Thu, 30 Jul 2026 15:00:43 +0200	[thread overview]
Message-ID: <b4fd3e49-e436-40cd-8b62-0c6792cd6f14@mailbox.org> (raw)
In-Reply-To: <DKBWUZLGTNVG.ZNWPY3U22BE8@smile.fr>

On 7/30/26 2:39 PM, Yoann Congal wrote:

Hello everyone,

>>> The fitimage fixes landed in oe-core master 6 weeks ago and they fix
>>> fitImage usability issues which block me from updating to wrynose in
>>> multiple projects, that's why I keep monitoring this thread so, but
>>> again, please do not read this as a push.
>>
>> I think going with the four patches from
>> https://lore.kernel.org/all/cover.1784364567.git.yoann.congal@smile.fr/
>> without a fifth patch which adds test coverage for this fairly isolated
>> detail is fine.
> 
> This is where I disagree. Last time I reviewed this series it looked
> good but I had no way to check it actually worked once backported to
> wrynose. That is why I asked Ryan to backport the test from master to
> wrynose.

Is there a git tree/branch with those patches ? If so, I can at least 
test this locally and confirm whether or not anything is broken on my end ?

>> Important is: We need 4 not only 3 patches:
>>
>> Adrian Freihofer (1):
>>    oe-selftest: fitimage: Do not expect kernel property in DTBO config
>>      subnodes
>>
>> Marek Vasut (2):
>>    kernel-fit-image.bbclass: Do not include kernel property in DTBO
>>      config subnodes
>>    kernel-fit-image.bbclass: Fix operation with KERNEL_DTBVENDORED = "1"
>>
>> Ryan Eatmon (1):
>>    kernel-fit-image: Add KERNEL_DTBVENDORED support for
>>      FIT_CONF_DEFAULT_DTB
> 
> Yes. This is the patches I have for this work.
> 
>> And also important is: We need time for testing on master before back-
>> porting to stable. Six weeks is probably enough. But the exact same
>> pattern ended up with a broken stable branch maybe one year ago. And
>> also this time there was a state on master which was at least
>> incomplete (three instead of four patches). But still, I think this is
>> ready for stable now.
> 
> I agree on the series needing testing. One more argument for waiting for
> a wrynose test.
> See https://lore.kernel.org/all/DK3HWGV0JCOP.14DJEFKWLP67L@smile.fr/
> (from the same thread you linked)

I ran this now and got 8 commits which cleanly apply on the wrynose 
branch, maybe that is all that is missing for the test part ?

$ git log --oneline --reverse --grep=fitimage 
origin/wrynose..origin/master -- meta/lib/oeqa/selftest/cases/fitimage.py
e46d8473fb3 oeqa/selftest/fitimage: fix missing whitespace around assignment
0344e652a40 oe-selftest: fitimage: replace _gen_random_file with 
_gen_elf64_dummy
5592be53348 oe-selftest: fitimage: replace bbb-dtbs-as-ext with 
test-dtbs-as-ext
befc103a95d oe-selftest: fitimage: replace MACHINE==qemux86-64 guards 
with KERNEL_SETUP_BIN
4b08cf6048b oe-selftest: fitimage: add machine settings table and skip 
helpers
f17f4263c07 oe-selftest: fitimage: stop hardcoding MACHINE and DISTRO in 
tests
85e0408a81b oe-selftest: fitimage: Do not expect kernel property in DTBO 
config subnodes
de2e11e6362 oe-selftest: fitimage: Add tests for KERNEL_DTBVENDORED

-- 
Best regards,
Marek Vasut


  reply	other threads:[~2026-07-30 13:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30  7:43 [wrynose][PATCH] kernel-fit-image.bbclass: Do not include kernel property in DTBO config subnodes Marek Vasut
2026-06-30 10:51 ` Freihofer, Adrian
2026-06-30 12:58   ` Marek Vasut
2026-07-02 11:26     ` Yoann Congal
2026-07-02 11:38       ` [OE-core] " adrian.freihofer
2026-07-04 21:55         ` Marek Vasut
2026-07-20 15:09           ` Marek Vasut
2026-07-20 15:19             ` Yoann Congal
2026-07-20 15:31               ` Marek Vasut
2026-07-29 22:31                 ` Marek Vasut
2026-07-30  7:36                   ` Yoann Congal
2026-07-30 11:52                     ` Marek Vasut
2026-07-30 12:19                       ` adrian.freihofer
2026-07-30 12:39                         ` Yoann Congal
2026-07-30 13:00                           ` Marek Vasut [this message]
2026-07-30 13:23                             ` adrian.freihofer
2026-07-30 13:49                               ` Yoann Congal

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=b4fd3e49-e436-40cd-8b62-0c6792cd6f14@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=adrian.freihofer@gmail.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=reatmon@ti.com \
    --cc=yoann.congal@smile.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.