Re: [6.2][regression] after commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae stopping working wifi mt7921e

From: Kalle Valo <kvalo@kernel.org>
To: "Linux kernel regression tracking \(Thorsten Leemhuis\)" 
	<regressions@leemhuis.info>
Cc: Felix Fietkau <nbd@nbd.name>,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
	lorenzo@kernel.org, sujuan.chen@mediatek.com,
	Linux List Kernel Mailing <linux-wireless@vger.kernel.org>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	spasswolf@web.de
Subject: Re: [6.2][regression] after commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae stopping working wifi mt7921e
Date: Fri, 13 Jan 2023 16:11:10 +0200	[thread overview]
Message-ID: <87358ecyo1.fsf@kernel.org> (raw)
In-Reply-To: <0078a5ff-2bc5-4b14-2735-1641feb46544@leemhuis.info> (Linux kernel regression tracking's message of "Tue, 10 Jan 2023 09:41:10 +0100")

"Linux kernel regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info> writes:

> On 10.01.23 09:00, Felix Fietkau wrote:
>
>>> Still no reply. I wonder if I'm holding things wrong. But well, let's
>>> wait one more day before escalating this further.
>> 
>> Johannes told me on IRC that he will review my patch soon. He simply has too many things to do at the moment.
>
> Great, thx. And sorry for prodding so much, but that is part of the job
> when it takes so long to fix regressions -- even in cases where that's
> mainly caused by a holiday season (which I took into account, otherwise
> I likely would have made more noise earlier already).

Thorsten, I value your work A LOT, tracking regressions is important and
makes our work easier. Thank you for that. But when tracking bugs please
be reasonable as well. Most of the people in the community are
volunteers, we have our normal lives/work as well and things don't
always move so fast. For example, I just came from a long vacation this
Monday and have a lot to catch up. That's why the release cycle is so
long as it is.

We are in -rc3 at the moment and I don't see the need to push the panic
button so early in the cycle. If we take fixes in a rush that might
break even more stuff. And anyone using release candidates ("rc") should
understand that things can be broken and it might take some time to get
them fixed, especially on holiday periods.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches