public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: Andrey Batyiev <batyiev@gmail.com>,
	linux-wireless@vger.kernel.org,
	Greg KH <gregkh@linuxfoundation.org>,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	Kalle Valo <kvalo@kernel.org>, Alf Marius <post@alfmarius.net>
Subject: Re: [REGRESSION] The iwl4965 driver broke somewhere between 6.10.10 and 6.11.5 (probably 6.11rc)
Date: Thu, 14 Nov 2024 21:36:06 +0100	[thread overview]
Message-ID: <87bjyhr1s9.fsf@toke.dk> (raw)
In-Reply-To: <8a647709-8c33-4ac9-92da-bbf83ae2ed93@leemhuis.info>

Hi Thorsten

Quoting a bit selectively and out of order to comment on a few unrelated
aspects of this (meta-)discussion:

Thorsten Leemhuis <regressions@leemhuis.info> writes:
> On 14.11.24 10:52, Johannes Berg wrote:
>> On Thu, 2024-11-14 at 10:24 +0100, Linux regression tracking (Thorsten
>> Leemhuis) wrote:
>>>
>>> Sigh.
>> 
>> Please. You really should consider adjusting your attitude on all this. 
>
> If the revert is only merged during the merge window, it will likely
> take [...] four additional weeks if we are really unlucky.
>
> Things like that bother me -- and thus, yes, sorry, also influence my
> attitude, which lead to the quoted "sigh". It's just that "fixes are
> there, they just take a long time to reach mainline and stable releases"
> is the biggest problem I see during my regression tracking work.

I understand your frustration, certainly, and I get that you are tasked
with a thankless job in trying to improve the regression handling
situation. However, I also agree with Johannes that by letting your
frustration shine through (which is basically what you're doing with
that "sigh"), you are turning a general frustration at a difficult
systemic problem into animosity towards the *person* you are directing
your email at. This comes across as incredibly condescending, and it
only fosters animosity in the other direction, even creating a perverse
incentive to just ignore regressions entirely, as Johannes also pointed
out in his follow-up email[0].

Or to put it another way: the actual patch being discussed here should
be held up as an example of a *successful* regression handling: A
relatively obscure issue was reported, and within a week a fix was
committed to the relevant subsystem tree. If we had been *anywhere* else
in the cycle than where we are right now, this would have percolated up
to Linus' tree in time for the next -rc, or at the very latest one week
later. Judging from the numbers you presented at LPC, this would be a
very timely fix in all cases.

So yes, it's unfortunate that this happened to land at an unlucky time
in the cycle, and yes, in the ideal world this would just have been
fast-tracked. But by reacting with frustration to something that, for
all intents and purposes, is a proper and timely handling of a
regression, you are antagonising people and hurting your cause, not
helping it.

As for a concrete suggestion for how this could have been handled
better, if you had followed up your "Many thx for taking care of this!"
(which was great!) with a "I noticed there's an opportunity to get this
in before 6.12 is released, which will mean this gets to users several
weeks faster. Would you mind asking Linus to (cherry-pick/pull) this out
of order, as he has indicated he is willing to do", instead of the
"sigh, you are doing this wrong", you would have a much higher chance of
actually getting results.


As a side note, on this point...

> My approach/attitude is based on actions from Linus and/or what I expect
> he wants me to do, so let's bring him in to give him a chance to state
> if I went to far here.

...I will add that I personally find the whole "appeal to authority"
approach you are taking with the regression handling processes to be
somewhat off-putting. "Because Linus says so" is a terrible argument for
doing anything (on its own). If you can't persuade people by the
strength of your argument, appealing to authority will at best get you
grudging least-effort compliance, and at worst it will be actively
harmful because you antagonise people.

And yes, convincing people to change the way they work is hard,
especially when the ask is for them to do *more* work. That doesn't mean
it is impossible, but it takes time and patience and a variety of
approaches to succeed in the long term.


Note that I am saying all of the above as someone who is generally
sympathetic to the goals of your work (as I am sure you are aware, since
you're using my exchange with Linus about this in your slides :)). I do
not believe you are trying to antagonise people on purpose, so please
view the above as a good faith attempt at providing some feedback on how
you can continue this work without ending up doing so unintentionally.

-Toke

[0] https://lore.kernel.org/r/35bee1c6146cf261ad6b47f585a5b454ad0763ec.camel@sipsolutions.net

  parent reply	other threads:[~2024-11-14 20:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <60f752e8-787e-44a8-92ae-48bdfc9b43e7@app.fastmail.com>
2024-11-06 11:22 ` [REGRESSION] The iwl4965 driver broke somewhere between 6.10.10 and 6.11.5 (probably 6.11rc) Kalle Valo
2024-11-06 17:13   ` Andrey Batyiev
2024-11-06 19:27     ` Alf Marius
2024-11-14  7:32       ` Kalle Valo
2024-11-14  9:24         ` Linux regression tracking (Thorsten Leemhuis)
2024-11-14  9:52           ` Johannes Berg
2024-11-14 10:18             ` Johannes Berg
2024-11-14 15:30             ` Thorsten Leemhuis
2024-11-14 15:59               ` Johannes Berg
2024-11-14 20:36               ` Toke Høiland-Jørgensen [this message]
2024-11-15 10:55                 ` Linux regression tracking (Thorsten Leemhuis)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bjyhr1s9.fsf@toke.dk \
    --to=toke@kernel.org \
    --cc=batyiev@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=post@alfmarius.net \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox