From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
Yash.Shinde@windriver.com,
openembedded-core@lists.openembedded.org,
Naveen.Gowda@windriver.com, Sundeep.Kokkonda@windriver.com
Subject: Re: [PATCH v2 2/3] rust: Upgrade 1.75.0->1.76.0
Date: Mon, 17 Jun 2024 16:14:28 +0200 [thread overview]
Message-ID: <20240617141428f7352c56@mail.local> (raw)
In-Reply-To: <708c2d0b-d578-46c6-a19d-c169f5a5750b@windriver.com>
On 17/06/2024 09:31:19-0400, Randy MacLeod wrote:
> On 2024-06-17 5:43 a.m., Alexander Kanavin wrote:
> > I have to ask, why 1.75.0->1.76.0? Can we go straight to $latest,
> > which is 1.79.0 as of now? It's a significant additional effort to do
> > incremental updates, and we've fallen so behind that it's perhaps
> > better to try to catch up fully.
> >
> > Alex
>
>
> Yash and Sundeep have updated and tested 1.76, 1.77, 1.78, 1.79 locally
> and have not seen any problems. As you know, the situation is
> often different when things are tested on the YP autobuilder. The idea
> is to test each update so that if there's a reproducability problem or
> some other AB specific problem, we have a smaller delta to investigate.
>
> That said, if Alexandre wants the full series up updates in one
> series and sees that 1.79 works, we can try that.
>
> If there are problems with 1.79 Alex could then test each update
> individually in master-next.
>
> Alexandre, what do you want to do?
I can take a series of incremental patches and I'll bisect if there are
any issues.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-06-17 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 16:04 [PATCH v2 1/3] rust: Oe-selftest fixes for rust v1.76 Yash.Shinde
2024-06-15 16:04 ` [PATCH v2 2/3] rust: Upgrade 1.75.0->1.76.0 Yash.Shinde
2024-06-17 9:43 ` Alexander Kanavin
2024-06-17 13:31 ` Randy MacLeod
2024-06-17 13:42 ` [OE-core] " Alexander Kanavin
2024-06-17 14:14 ` Alexandre Belloni [this message]
2024-06-17 15:59 ` Randy MacLeod
2024-06-17 16:53 ` Alexandre Belloni
2024-06-17 14:42 ` Sundeep KOKKONDA
2024-06-15 16:04 ` [PATCH v2 3/3] rust: reproducibility issue fix with v1.76 Yash.Shinde
2024-06-17 9:41 ` 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=20240617141428f7352c56@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=Naveen.Gowda@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=Yash.Shinde@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.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