From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [RFT][PATCH 1/2] glibc: Upgrade to 2.40
Date: Mon, 22 Jul 2024 17:36:52 +0100 [thread overview]
Message-ID: <90ef6669ed9ada15d6db57cdb24059178bf86207.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sroJs_73HtyVYszWog2dr3zrUgsJqmF5+SourfUcg9+ow@mail.gmail.com>
On Mon, 2024-07-22 at 07:18 -0700, Khem Raj wrote:
>
>
> On Mon, Jul 22, 2024 at 2:22 AM Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > On Sun, 2024-07-21 at 11:03 -0700, Khem Raj via lists.openembedded.org wrote:
> >
> > Thanks Khem. I ran this through the autobuilder and there were only two
> > failures. One expected as it tests the buildtools libc which doesn't
> > work until we upgrade uninative. The other looks to be an intermittent
> > qemuarm failure. From my perspective I think we're looking good to
> > merge this!
> >
>
>
>
> Cool yeah and today the release also came out so I am not expecting to make any more changes to the RFT series
>
I've gone ahead and merged it which lets us proceed with a uninative
build/release.
Cheers,
Richard
next prev parent reply other threads:[~2024-07-22 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 18:03 [RFT][PATCH 1/2] glibc: Upgrade to 2.40 Khem Raj
2024-07-21 18:03 ` [RFT][PATCH 2/2] glibc: Remove redundant configure option --disable-werror Khem Raj
2024-07-22 9:22 ` [OE-core] [RFT][PATCH 1/2] glibc: Upgrade to 2.40 Richard Purdie
2024-07-22 14:18 ` Khem Raj
2024-07-22 16:36 ` Richard Purdie [this message]
2024-07-22 16:41 ` Khem Raj
2024-09-04 1:47 ` Maohui Lei (Fujitsu)
2024-09-04 3:18 ` Khem Raj
2024-09-04 8:59 ` Maohui Lei (Fujitsu)
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=90ef6669ed9ada15d6db57cdb24059178bf86207.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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