From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yash.Shinde@windriver.com,
openembedded-core@lists.openembedded.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Randy.MacLeod@windriver.com, Naveen.Gowda@windriver.com,
Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH 2/2] rust: Upgrade 1.78.0->1.79.0
Date: Tue, 27 Aug 2024 11:38:56 +0100 [thread overview]
Message-ID: <bbbe564b9b6191edbe62abd69fa3b337ada2ad4a.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240825170553.566798-2-Yash.Shinde@windriver.com>
On Sun, 2024-08-25 at 10:05 -0700, Yash Shinde via
lists.openembedded.org wrote:
> From: Yash Shinde <Yash.Shinde@windriver.com>
>
> Update the patch files with rust v1.79.0.
>
> Drop the following backported patch which is merged
> with rust v1.79 upgrade.
>
> - cross-targets-backport.patch
>
> https://blog.rust-lang.org/2024/06/13/Rust-1.79.0.html
>
> Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com>
It seems mostly ok but we did see:
https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/9385/steps/13/logs/stdio
in Alexandre's build :(
Cheers,
Richard
next prev parent reply other threads:[~2024-08-27 10:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 17:05 [PATCH 1/2] rust: Oe-selftest changes for rust v1.79 Yash.Shinde
2024-08-25 17:05 ` [PATCH 2/2] rust: Upgrade 1.78.0->1.79.0 Yash.Shinde
2024-08-27 10:38 ` Richard Purdie [this message]
2024-08-27 12:11 ` [OE-core] " Yash Shinde
2024-08-27 12:24 ` Alexander Kanavin
2024-08-27 12:40 ` Richard Purdie
2024-08-27 12:47 ` Yash Shinde
2024-08-27 13:22 ` Richard Purdie
2024-08-27 16:23 ` Alexander Kanavin
[not found] ` <17EFA275ACF95534.20373@lists.openembedded.org>
2024-08-27 16:25 ` Alexander Kanavin
[not found] ` <17EFA28FD32C2C48.20373@lists.openembedded.org>
2024-08-27 17:16 ` Alexander Kanavin
2024-08-27 19:51 ` Richard Purdie
2024-08-27 20:38 ` Alexander Kanavin
2024-08-27 20:41 ` Richard Purdie
2024-08-27 20:47 ` Alexander Kanavin
2024-08-27 21:02 ` Khem Raj
2024-08-28 13:11 ` Alexander Kanavin
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=bbbe564b9b6191edbe62abd69fa3b337ada2ad4a.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Naveen.Gowda@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=Yash.Shinde@windriver.com \
--cc=alexandre.belloni@bootlin.com \
--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