From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Jon Mason" <jon.mason@arm.com>, "Ross Burton" <ross.burton@arm.com>
Cc: <festevam@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2] u-boot: upgrade 2026.01 -> 2026.04
Date: Fri, 10 Apr 2026 15:43:48 +0200 [thread overview]
Message-ID: <DHPIPLRXIPB1.299V6FDJVU86@bootlin.com> (raw)
In-Reply-To: <20260408114523.112252-1-festevam@gmail.com>
On Wed Apr 8, 2026 at 1:45 PM CEST, Fabio Estevam via lists.openembedded.org wrote:
> Upgrade to U-Boot 2026.04.
>
> Remove the CVE-2026-33243.patch as it is already applied in 2026.04.
>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
Hi Jon, Ross,
I just want to let you now some patches in meta-arm will have to be
dropped or refreshed once this upgrade is merged in master:
ERROR: u-boot-1_2026.04-r0 do_patch: QA Issue: Fuzz detected:
Applying patch 0003-vexpress64-Imply-CONFIG_ARM64_CRC32-by-default.patch
https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/3451
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-04-10 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 11:45 [PATCH v2] u-boot: upgrade 2026.01 -> 2026.04 Fabio Estevam
2026-04-10 13:43 ` Mathieu Dubois-Briand [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-22 10:36 [OE-core] [PATCH] python3-cryptography(-vectors): upgrade 46.0.5 -> 46.0.7 Wang Mingyu
2026-04-22 10:36 ` [OE-core] [PATCH v2] u-boot: upgrade 2026.01 -> 2026.04 Wang Mingyu
2026-04-22 11:07 ` Fabio Estevam
2026-04-22 11:53 ` Paul Barker
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=DHPIPLRXIPB1.299V6FDJVU86@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=festevam@gmail.com \
--cc=jon.mason@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.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 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.