On Thu, 5 Nov 2026 07:32:05 +0100 [email protected] wrote:
> On Wed, 4 Nov 2026 20:48:14 +0100 Uwe =?utf-8?Q?Kleine-K=C3=B6nig?=
> <[email protected]> wrote:
> > Control: tag -1 + moreinfo
> >
> > Hello Ole,
> >
> > On Fri, Oct 23, 2026 at 04:12:41PM +0200, [email protected]
wrote:
> > > I have finished the bisect compile and testing and the log file is
> attached.
> >
> > Thanks for going through that. The result of the --first-parent
> > bisection is unfortunately not the offending commit but only the merge
> > when Linus Torvalds tree got bad during the v7.1 development cycle.
(The
> > upside of using --first-parent is that the individual steps are cheaper
> > in build time.)
> >
> > So can you please repeat the procedure starting with:
> >
> > git bisect start 4a57e0913e8c7fff407e97909f4ae48caa84d612^2
> 028ef9c96e96197026887c0f092424679298aae8
> >
> > to pinpoint the actual commit? Don't be irritated by the first tree to
> > check (v7.0-rc7), that's the common merge base.
> >
> > Best regards
> > Uwe
>
> Hi Uwe
>
> that might be a little bad as i have deleted the whole setup as i
> thought i was finished :-(
>
> do i need to start all over (i can do that) or is there a way to get to
> the right bisect to start with?
>
> --
> Ole
and there is, sorry ... you literally wrote it :-)
i will test asap
--
Ole
