Re: [PATCH v2 2/3] rust: Upgrade 1.75.0->1.76.0

[Alexandre Belloni <alexandre.belloni@bootlin.com>]

On 17/06/2024 11:59:25-0400, Randy MacLeod wrote:
> On 2024-06-17 10:14 a.m., Alexandre Belloni wrote:
> > 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.
> > 
> > 
> Super.
> 
> I stand corrected in that we only have up to 1.78 locally.
> 
> 
> Also, Richard does NOT want to update master until we've resolved the
> 1.75 reproducability problem so that we can easily backport that to
> scarthgap
> and so that there's some additional pressure to get that bug resolved.
> 
> 
> Alexandre,
> Do you want to test the 1.75 to 1.78 series in master-next ONLY so that we
> see if
> there are additional reproducability problems?

Yes, I'll base that directly on top of master to ensure there are no
other patches causing issues.

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com