Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	mikko.rapeli@linaro.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3] u-boot: upgrade 2025.04 -> 2025.07
Date: Mon, 21 Jul 2025 07:48:30 -0600	[thread overview]
Message-ID: <20250721134830.GC193579@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5CaSgkYjTVk2WcQCoWvRNNGkXRV2bp9BdAU=mkQR8Rg+w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 781 bytes --]

On Mon, Jul 21, 2025 at 09:34:10AM -0300, Fabio Estevam wrote:
> Adding Tom.
> 
> On Sat, Jul 19, 2025 at 3:34 AM Mathieu Dubois-Briand
> <mathieu.dubois-briand@bootlin.com> wrote:
> >
> > On Fri Jul 18, 2025 at 11:01 AM CEST, Mikko Rapeli via lists.openembedded.org wrote:
> > > From: Fabio Estevam <festevam@gmail.com>
> > >
> > > Upgrade to U-Boot 2025.07. Added patches for build race conditions.
> > > Removed qemu KVM USB workaround since issue is fixed upstream.

Here's the problem. Yes, the "KVM USB workaround" was fixed upstream.
But it's not in v2025.07. You need to cherry-pick:

fcc60481ae75 qemu: arm: Enable virtualizable IO accessors
dc512700ad46 arm: io.h: Fix io accessors for KVM
b56c0632ad62 nxp: Prepare macros for KVM changes

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2025-07-21 13:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  9:01 [PATCH v3] u-boot: upgrade 2025.04 -> 2025.07 Mikko Rapeli
2025-07-18 10:28 ` [OE-core] " Richard Purdie
2025-07-18 10:34   ` Quentin Schulz
2025-07-18 11:16     ` Richard Purdie
2025-07-19  6:34 ` Mathieu Dubois-Briand
2025-07-21 12:34   ` Fabio Estevam
2025-07-21 13:48     ` Tom Rini [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=20250721134830.GC193579@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=festevam@gmail.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=mikko.rapeli@linaro.org \
    --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