From: Kalle Valo <kvalo@kernel.org>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Gregory Greenman <gregory.greenman@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Ayala Beker <ayala.beker@intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: Mark IWLMEI as broken
Date: Fri, 09 Sep 2022 12:10:08 +0300 [thread overview]
Message-ID: <87o7vo9amn.fsf@kernel.org> (raw)
In-Reply-To: <87o7vpcbbo.fsf@toke.dk> ("Toke \=\?utf-8\?Q\?H\=C3\=B8iland-J\?\= \=\?utf-8\?Q\?\=C3\=B8rgensen\=22's\?\= message of "Fri, 09 Sep 2022 08:26:51 +0200")
Toke Høiland-Jørgensen <toke@toke.dk> writes:
> Kalle Valo <kvalo@kernel.org> writes:
>
>> Toke Høiland-Jørgensen <toke@toke.dk> writes:
>>
>>> forthcoming. Since just disabling the iwlmei driver works as a workaround,
>>> let's mark the config option as broken until it can be fixed properly.
>>>
>>> [0] https://bugzilla.kernel.org/show_bug.cgi?id=215937
>>
>> So does the bug only happen with iwd? Should I mention that in the
>> commit log? It would be good to describe the conditions when the bug
>> happens.
>
> Well, what happens is that the interface ends up in the 'down' state
> after coming back from suspend. And iwd doesn't touch the interface
> state, but wpa_supplicant does, so the user-visible "my WiFi doesn't
> work" thing only happens on iwd...
Thanks, I'll mention that in the commit log.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-09-09 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 13:44 [PATCH] iwlwifi: Mark IWLMEI as broken Toke Høiland-Jørgensen
2022-09-08 8:27 ` Emmanuel Grumbach
2022-09-08 9:18 ` Toke Høiland-Jørgensen
2022-09-12 11:19 ` Kalle Valo
2022-09-09 5:42 ` Kalle Valo
2022-09-09 6:26 ` Toke Høiland-Jørgensen
2022-09-09 9:10 ` Kalle Valo [this message]
2022-09-09 6:54 ` Emmanuel Grumbach
2022-09-12 11:24 ` wifi: " Kalle Valo
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=87o7vo9amn.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ayala.beker@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=gregory.greenman@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=toke@toke.dk \
/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