From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross.burton@arm.com>,
"anuj.mittal@intel.com" <anuj.mittal@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 4/4] grub2: upgrade 2.06 -> 2.12
Date: Wed, 24 Jan 2024 16:22:49 +0000 [thread overview]
Message-ID: <b72c96006e0711b704577ab9038d39bdc935a30b.camel@linuxfoundation.org> (raw)
In-Reply-To: <A950FDEA-F17E-4234-AFE4-563163121E62@arm.com>
On Wed, 2024-01-24 at 13:50 +0000, Ross Burton wrote:
> On 23 Jan 2024, at 08:47, Anuj Mittal via lists.openembedded.org <anuj.mittal=intel.com@lists.openembedded.org> wrote:
> >
> > Drop patches that have been upstreamed. Refresh others.
>
> I was nervous but I’m pleased to say:
>
> Tested-by: Ross Burton <ross.burton@arm.com <mailto:ross.burton@arm.com>>
>
> For the upgrade on the fvp-base aarch64 machine.
>
> Thanks Anuj!
I was really happy to see this upgrade arrive too. It was on my radar
as something we definitely wanted to get into 5.0 since it lets us drop
a lot of patches from what might have been the most patched recipe in
OE-Core.
Thanks Anuj :)
Cheers,
Richard
prev parent reply other threads:[~2024-01-24 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 8:47 [PATCH 1/4] bluez5: upgrade 5.71 -> 5.72 Anuj Mittal
2024-01-23 8:47 ` [PATCH 2/4] cronie: upgrade 1.7.0 -> 1.7.1 Anuj Mittal
2024-01-23 8:47 ` [PATCH 3/4] libpsl: upgrade 0.21.2 -> 0.21.5 Anuj Mittal
2024-01-23 8:47 ` [PATCH 4/4] grub2: upgrade 2.06 -> 2.12 Anuj Mittal
2024-01-24 13:50 ` [OE-core] " Ross Burton
2024-01-24 16:22 ` Richard Purdie [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=b72c96006e0711b704577ab9038d39bdc935a30b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=anuj.mittal@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox