public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Alf Marius" <post@alfmarius.net>
Cc: "Andrey Batyiev" <batyiev@gmail.com>,
	 regressions@lists.linux.dev, linux-wireless@vger.kernel.org
Subject: Re: [REGRESSION] The iwl4965 driver broke somewhere between 6.10.10 and 6.11.5 (probably 6.11rc)
Date: Thu, 14 Nov 2024 09:32:02 +0200	[thread overview]
Message-ID: <87ttcauv7x.fsf@kernel.org> (raw)
In-Reply-To: <4f689121-f2c1-45ec-bd5b-105a770af935@app.fastmail.com> (Alf Marius's message of "Wed, 06 Nov 2024 20:27:40 +0100")

"Alf Marius" <post@alfmarius.net> writes:

> Good evening folks :)
>
> [Andrey Batyiev]
>> Hello everyone,
>> I've only tested it on my 3945. I have no equipment to test it on 4965, sorry.
>
> Yes the commit message says "Tested on iwl3945 only."
> ..which I did find a bit strange. Is it normal to deploy code to the mainline
> that is untested? Why was this also applied to 4965?
>
> I'm just asking questions here, as I have no direct knownledge of C or
> kernel driver programming. I've 20 yrs of web-dev experience though
> and know from experience that shipping untested code is a bad idea.
>
> Anyway, not trying to point fingers here! Just curious to find those who
> wrote the actual code, maybe get some info on why this was added
> and if it is really important. If not, maybe a revert is in order
>
> Regarding testing, I obviously have a laptop with the 4965 card and
> I'm more than willing to test stuff out if needed.

I sent a revert to fix this:

https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/commit/?id=11597043d74809daf5d14256b96d6781749b3f82

If all goes well this should be in v6.13-rc1.

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

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

  reply	other threads:[~2024-11-14  7:32 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 [this message]
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
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=87ttcauv7x.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=batyiev@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=post@alfmarius.net \
    --cc=regressions@lists.linux.dev \
    /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