[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <znkp6x44lnrvn4c7xnb43kiwfmyp3ovsnzi37xgaw3eyvgcm6z@pfxbrniec7jf>
Date: Mon, 7 Oct 2024 16:38:26 +0200
From: Uwe Kleine-König <u.kleine-koenig@...libre.com>
To: Diederik de Haas <didi.debian@...ow.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arnd Bergmann <arnd@...db.de>, Armin Wolf <W_Armin@....de>, Guenter Roeck <linux@...ck-us.net>,
Vinod Koul <vkoul@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: Error "ee1004 3-0050: probe with driver ee1004 failed with error
-5" since 6.11
Hello Diederik,
On Sat, Sep 28, 2024 at 08:54:12AM +0200, Diederik de Haas wrote:
> On Fri Sep 27, 2024 at 11:59 PM CEST, Uwe Kleine-König wrote:
> > [ extensive description on what to do when git bisect results
> > in a merge commit as 'first bad commit' ]
>
> This is awesome, thank you very much :)
Were you able to understand that, or did you just bookmark it for the
next time? If you still have questions, don't hesitate to ask.
> I haven't made up my mind yet whether I'll apply it to this specific
> issue. It doesn't cause any actual problems (AFAICT) and most
> importantly, it seems to be fixed in 6.12(-rc1) already.
> And the 6.11 kernel is only a 'temporary' one which I don't care (much)
> about, while it is fixed in the kernel I do care about (6.12).
It might be beneficial to find the commit between 6.11 and 6.12-rc1
that's fixing the issue. That would allow to backport the fix to 6.11.x.
(No need for a complicated procedure as I described, just bisect between
6.11 and 6.12-rc1 (maybe with "new" and "old" instead of "bad" and
"good" for less confusion)).
Best regards
Uwe
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists