Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: joaomarcos.costa@bootlin.com, dmitry.baryshkov@oss.qualcomm.com,
	Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
Cc: michael.opdenacker@rootcommit.com,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] u-boot: move DT validation yaml removal patch to common SRC_URI
Date: Mon, 18 May 2026 21:40:51 +0200	[thread overview]
Message-ID: <9dc8c3b7-c358-4a7d-af1a-c1aec83906af@rootcommit.com> (raw)
In-Reply-To: <f531466a-fbd8-472b-a2b1-e487eea6d51a@bootlin.com>

Greetings,

On 5/9/26 12:55 AM, Joao Marcos Costa via lists.openembedded.org wrote:
> Hello,
>
> On 5/8/26 21:09, Dmitry Baryshkov via lists.openembedded.org wrote:
> (...)
>>
>> We are fetching the source basing on the PV. The patch might be
>> applicable or might not. I'd suggest listing the patch twice: in the
>> u-boot_2026.04.bb and u-boot-tools_2026.04.bb.
>>
>> (in fact I did that in a local patch, it's good that I checked the ML
>> before sending it).
>
> I agree with this approach. Also, even if someone does not like seeing 
> the same patch applied in two different recipes, the patch was already 
> merged upstream and should be available in v2026.05 (I hope?). So, in 
> any case, we will drop it soon enough.


Any update on this patch?
Building u-boot-tools on master for the "qemuriscv64" machine is still 
broken.

For people facing this too, a workaround is the add back 
"libyaml-native" to depends in meta/recipes-bsp/u-boot/u-boot-common.inc

How come the autobuilder didn't catch this issue on one of our 
officially supported machines?
Cheers
Michael.

-- 
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com



  reply	other threads:[~2026-05-18 19:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 20:40 [PATCH] u-boot: move DT validation yaml removal patch to common SRC_URI Ricardo Salveti
2026-05-08 14:35 ` [OE-core] " Quentin Schulz
2026-05-08 16:04   ` Ricardo de Araujo (Salveti)
2026-05-08 22:51   ` Joao Marcos Costa
2026-05-08 23:43     ` Ricardo de Araujo (Salveti)
2026-05-08 19:09 ` Dmitry Baryshkov
2026-05-08 20:57   ` Ricardo de Araujo (Salveti)
2026-05-08 22:55   ` [OE-core] " Joao Marcos Costa
2026-05-18 19:40     ` Michael Opdenacker [this message]
2026-05-19 11:59       ` Joao Marcos Costa
2026-05-19 16:29         ` Michael Opdenacker
2026-05-19 17:01           ` Ricardo de Araujo (Salveti)
2026-05-19 20:25             ` Dmitry Baryshkov
2026-05-20  8:10               ` Joao Marcos Costa
2026-05-20  0:21 ` [PATCH v2] u-boot: move DT validation yaml removal patch to SRC_URI Ricardo Salveti

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=9dc8c3b7-c358-4a7d-af1a-c1aec83906af@rootcommit.com \
    --to=michael.opdenacker@rootcommit.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=joaomarcos.costa@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ricardo.salveti@oss.qualcomm.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