All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kurt Borja" <kuurtb@gmail.com>
To: "Kurt Borja" <kuurtb@gmail.com>,
	"Miri Korenblit" <miriam.rachel.korenblit@intel.com>,
	"Johannes Berg" <johannes.berg@intel.com>,
	"Emmanuel Grumbach" <emmanuel.grumbach@intel.com>
Cc: <linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wifi: iwlwifi: Fix iwl_pci_probe() regression
Date: Tue, 15 Apr 2025 11:50:23 -0300	[thread overview]
Message-ID: <D97AOGEOKCRX.2LAIZUEPNX2E@gmail.com> (raw)
In-Reply-To: <20250329-wifi-fix-v1-1-d6360e78f091@gmail.com>

On Sat Mar 29, 2025 at 1:48 AM -03, Kurt Borja wrote:
> Fix the following probing error:
>
> iwlwifi: No config found for PCI dev 2725/1674, rev=0x420, rfid=0x10d000
> iwlwifi 0000:3b:00.0: probe with driver iwlwifi failed with error -22
>
> Which happens, as the comment suggests, due to an extra `!` when
> comparing the device bandwidth with the no_160 subsystem flag.
>
> Fixes: 75a3313f52b7 ("wifi: iwlwifi: make no_160 more generic")
> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
> ---
> Hi all,
>
> After compiling and testing the latest commit on Linus's tree, I found
> that my wifi wasn't working. After bisecting I found:
>
> first bad commit: [75a3313f52b7e08e7e73746f69a68c2b7c28bb2b] wifi: iwlwifi: make no_160 more generic
>
> And the culprit was an extra `!` when getting the device info.
>
> This patch is based on the latest commit of Linus's tree.

Hi all,

Any updates on this?

-- 
 ~ Kurt

      reply	other threads:[~2025-04-15 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-29  4:48 [PATCH] wifi: iwlwifi: Fix iwl_pci_probe() regression Kurt Borja
2025-04-15 14:50 ` Kurt Borja [this message]

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=D97AOGEOKCRX.2LAIZUEPNX2E@gmail.com \
    --to=kuurtb@gmail.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.