From: Jeff Chua <jeff.chua.linux@gmail.com>
To: "Greenman, Gregory" <gregory.greenman@intel.com>
Cc: "bagasdotme@gmail.com" <bagasdotme@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"Berg, Johannes" <johannes.berg@intel.com>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: iwlwifi broken in post-linux-6.3.0 after April 26
Date: Mon, 1 May 2023 07:57:42 +0800 [thread overview]
Message-ID: <CAAJw_Zvafhng8oP8E6HyhB5DK-WSQm2_yNbbHhgbTQb74pM-fA@mail.gmail.com> (raw)
In-Reply-To: <0785e432f1776b3531e8e033cb5b48eeb58b12b6.camel@intel.com>
On Mon, May 1, 2023 at 2:00 AM Greenman, Gregory
<gregory.greenman@intel.com> wrote:
> > Strangely, I couldn't reproduce it on my system. But, anyway this feature
> > better be disabled for a while. I'll send a patch with a fix shortly.
> May I ask you to try this fix in [1] (also cc-ed you on the patch itself)?
>
> [1] https://lore.kernel.org/linux-wireless/20230430201830.2f8f88fe49f6.I2f0076ef1d1cbe5d10010549c875b7038ec4c365@changeid/
Hi Greg,
Applied the patch. It worked! Thank you!
Jeff
next prev parent reply other threads:[~2023-04-30 23:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230429020951.082353595@lindbergh.monkeyblade.net>
[not found] ` <CAAJw_ZueYAHQtM++4259TXcxQ_btcRQKiX93u85WEs2b2p19wA@mail.gmail.com>
2023-04-29 14:07 ` iwlwifi broken in post-linux-6.3.0 after April 26 Bagas Sanjaya
2023-04-29 18:17 ` Jeff Chua
2023-04-30 10:58 ` Jeff Chua
2023-04-30 17:06 ` Greenman, Gregory
2023-04-30 18:00 ` Greenman, Gregory
2023-04-30 23:57 ` Jeff Chua [this message]
2023-05-01 4:46 ` Bagas Sanjaya
2023-07-05 7:24 ` Linux-6.5 iwlwifi crash Jeff Chua
2023-07-05 8:37 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-05 11:56 ` Jeff Chua
2023-07-05 18:11 ` Larry Finger
2023-07-07 1:56 ` Jeff Chua
2023-07-07 8:43 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-07 9:48 ` Thorsten Leemhuis
2023-07-07 18:07 ` Larry Finger
2023-07-09 0:00 ` Jeff Chua
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=CAAJw_Zvafhng8oP8E6HyhB5DK-WSQm2_yNbbHhgbTQb74pM-fA@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregory.greenman@intel.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).