From: Paul Barker <paul@pbarker.dev>
To: festevam@gmail.com, wangmy@fujitsu.com,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] u-boot: upgrade 2026.01 -> 2026.04
Date: Wed, 22 Apr 2026 12:53:41 +0100 [thread overview]
Message-ID: <faddc25bf9184723e1e48df48b8bb85617132095.camel@pbarker.dev> (raw)
In-Reply-To: <CAOMZO5CmWHY2NTa-CLpJMPMpAw6ntuGgXAx5Pb1RY5Eke5SZmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
On Wed, 2026-04-22 at 08:07 -0300, Fabio Estevam via
lists.openembedded.org wrote:
> On Wed, Apr 22, 2026 at 7:36 AM wangmy via lists.openembedded.org
> <wangmy=fujitsu.com@lists.openembedded.org> wrote:
> >
> > From: Wang Mingyu <wangmy@fujitsu.com>
> >
> > CVE-2026-33243.patch
> > removed since it's included 2026.04
> >
> > Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
>
> I submitted the U-Boot upgrade on April 8th:
>
> https://lists.openembedded.org/g/openembedded-core/message/234837
>
> Not sure why it was not applied yet.
Hi Fabio,
We are currently in feature freeze for the upcoming 6.0 release. We will
resume applying upgrades after 6.0.
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2026-04-22 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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] python3-spdx-python-model: upgrade 0.0.4 -> 0.0.5 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-08 11:45 Fabio Estevam
2026-04-10 13:43 ` [OE-core] " Mathieu Dubois-Briand
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=faddc25bf9184723e1e48df48b8bb85617132095.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=festevam@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=wangmy@fujitsu.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