From: "Kokkonda, Sundeep" <sundeep.kokkonda@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] rust: Upgrade 1.66.0 -> 1.66.1
Date: Wed, 18 Jan 2023 09:39:48 -0800 [thread overview]
Message-ID: <17348.1674063588089824843@lists.openembedded.org> (raw)
In-Reply-To: <765d5133-42eb-2ef6-7ba0-b5556a7a1d1b@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
@Randy,
To summarize the discussion, I should try -
1. Upgrade Kirkstone/Lagdale rust to 1.66.1 and
2. backporting the fixes of Cargo/Rust for kirkstone (patches given in https://github.com/rust-lang/wg-security-response/tree/main/patches/CVE-2022-46176 )
Is this correct?
--
Sundeep K.
[-- Attachment #2: Type: text/html, Size: 538 bytes --]
next prev parent reply other threads:[~2023-01-18 17:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 6:40 [OE-Core][PATCH] rust: Upgrade 1.66.0 -> 1.66.1 Alex Kiernan
2023-01-12 23:07 ` Randy MacLeod
2023-01-16 11:41 ` [PATCH] " Kokkonda, Sundeep
2023-01-16 15:20 ` Kokkonda, Sundeep
2023-01-17 20:29 ` [OE-core] " Randy MacLeod
2023-01-17 21:54 ` Richard Purdie
2023-01-17 21:56 ` Randy MacLeod
2023-01-17 22:00 ` Alexander Kanavin
2023-01-17 22:37 ` Steve Sakoman
2023-01-18 2:07 ` Randy MacLeod
2023-01-18 7:45 ` Alexander Kanavin
2023-01-18 8:08 ` Mikko Rapeli
2023-01-18 10:12 ` Alex Kiernan
2023-01-18 17:39 ` Kokkonda, Sundeep [this message]
2023-02-02 18:06 ` Tim Orling
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=17348.1674063588089824843@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