[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <00d9ec8a-5a44-01ec-a51f-ac898152e22c@leemhuis.info>
Date: Tue, 4 Jul 2023 10:30:44 +0200
From: "Linux regression tracking #update (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Sardonimous <sardonimous@...mail.com>,
Larry Finger <Larry.Finger@...inger.net>,
Arnd Bergmann <arnd@...db.de>,
Bagas Sanjaya <bagasdotme@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
Linux Wireless <linux-wireless@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>
Cc: Michael Büsch <m@...s.ch>,
kernel test robot <lkp@...el.com>,
Simon Horman <simon.horman@...igine.com>,
Kalle Valo <kvalo@...nel.org>
Subject: Re: Fwd: After kernel 6.3.7 or 6.3.8 b43 driver fails
On 03.07.23 22:13, Sardonimous wrote:
> On 7/3/23 12:35 PM, Larry Finger wrote:
>> Sorry that it took so long to get back to you.
>>
>> For my ppc32, there is no regression. It took a while to learn the
>> pio=1 and qos=0 are BOTH needed. That I do not understand, but with
>> both set, the device works with kernel 6.4 and all earlier kernels
>> that I tried. Fortunately, I did not need to do the entire bisection.
>>
>> I am working on eliminating the warning that appears with qos=0, but
>> it does not inhibit operations.
>>
>> @Bagas Sanjaya: Please mark this "regression" as invalid.
>>
>> Larry
>>
> I appreciate the time you've spent on this.
Yeah, thx from my side, too.
#regzbot invalid: wasn't a regression after all
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
Powered by blists - more mailing lists