From: "Sundeep KOKKONDA" <sundeep.kokkonda@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] rust: Upgrade 1.70.0 -> 1.71.0
Date: Thu, 19 Oct 2023 08:22:41 -0700 [thread overview]
Message-ID: <6763.1697728961959755862@lists.openembedded.org> (raw)
In-Reply-To: <CAO5Uq5R-xvytNWqtfwRk7F3BEVMNWkwQwyybHsQjrd86ZMkSKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
Hi Alex,
We may look into rust oe-selftest issues during coming week.
FYI... We did rust upgrade to 1.73.0 and we could still see the "-Z nightly build flag" failure issue (which was initially observed with rust 1.72.0 upgrade). We will send the patch by tomorrow and you can consider that for your analysis.
Thanks,
Sundeep K.
[-- Attachment #2: Type: text/html, Size: 383 bytes --]
next prev parent reply other threads:[~2023-10-19 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 14:30 [PATCH v3] rust: Upgrade 1.70.0 -> 1.71.0 Yash.Shinde
2023-08-25 13:20 ` [OE-core] " Luca Ceresoli
2023-08-25 15:30 ` Shinde, Yash
2023-08-25 23:17 ` Randy MacLeod
2023-09-21 13:38 ` Shinde, Yash
2023-10-18 19:08 ` [OE-core] " Alex Kiernan
2023-10-19 15:22 ` Sundeep KOKKONDA [this message]
2023-10-20 15:54 ` Sundeep KOKKONDA
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=6763.1697728961959755862@lists.openembedded.org \
--to=sundeep.kokkonda@windriver.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