public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"lenb@kernel.org" <lenb@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi 0000:3a:00.0: Microcode SW error detected. Restarting 0x2000000.
Date: Thu, 13 Jan 2022 08:51:14 +0000	[thread overview]
Message-ID: <1b4e94531f48a6d58bf3502dbb7125075b96944d.camel@intel.com> (raw)
In-Reply-To: <CAJvTdKmKPA_W_tXVjFOQEb5nX+sE+PmBeyVcf35=8WbLXuZapA@mail.gmail.com>

On Wed, 2022-01-12 at 13:49 -0500, Len Brown wrote:
> On Wed, Jan 12, 2022 at 3:34 AM Johannes Berg <johannes@sipsolutions.net> wrote:
> 
> > Something like this might help?
> 
> Yes!
> I have confirmed that this patch allows wifi to work, when applied to
> Linux-5.16.
> 
> Let me know when you'd like me to test a production patch.

Thanks a lot for testing!

I just sent an official version of the fix (you are CCed).  It would be
great if you could test that one as well!

We'll get it into the v5.17-rc series and I CCed stable, so it should
land in v5.15 and v5.16 soon too.

Thanks for reporting and testing!

--
Cheers,
Luca.

  reply	other threads:[~2022-01-13  8:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  1:47 iwlwifi 0000:3a:00.0: Microcode SW error detected. Restarting 0x2000000 Len Brown
2022-01-12  8:34 ` Johannes Berg
2022-01-12  9:05   ` Coelho, Luciano
2022-01-12  9:27     ` Johannes Berg
2022-01-12  9:33       ` Coelho, Luciano
2022-01-12  9:35         ` Johannes Berg
2022-01-12  9:40           ` Coelho, Luciano
2022-01-12 14:58     ` Len Brown
2022-01-12 15:42       ` Coelho, Luciano
2022-01-12 18:14         ` Len Brown
2022-01-12 18:49   ` Len Brown
2022-01-13  8:51     ` Coelho, Luciano [this message]
2022-01-27 18:28     ` Coelho, Luciano

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=1b4e94531f48a6d58bf3502dbb7125075b96944d.camel@intel.com \
    --to=luciano.coelho@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=lenb@kernel.org \
    --cc=linux-wireless@vger.kernel.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