From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8538EECAAD3 for ; Fri, 9 Sep 2022 09:10:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232084AbiIIJKc (ORCPT ); Fri, 9 Sep 2022 05:10:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46734 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232090AbiIIJKX (ORCPT ); Fri, 9 Sep 2022 05:10:23 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C8739580BC for ; Fri, 9 Sep 2022 02:10:17 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D90EF61F46 for ; Fri, 9 Sep 2022 09:10:15 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 199CFC433D6; Fri, 9 Sep 2022 09:10:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1662714615; bh=IaWgpqu93sgkUECLoa0L6F6R7BhmK7L2O3GXCUn3v0c=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=fbr/JfcWTE11hBq29uZ5cf5LwpfcN9yO05il1E3t/4e+UJWUFiSpBFLp6u7mt+QWJ sB0Ena2zpj6MGhda5eoq+nuHUE0g4a3UHvOJVvLuFNPsze1rDF/bzzAGqMugJ/FTnM AlYPmXyAWqjfwdrrOhTY5Ez1pp/pLN9W+sFu+LCBeg8OM8AZfx9dz55Qg4uSJ9ZNhI lkDjRHkbyVkEGKXcXWjTj2XgEfYkO1n/yz1tUCjgPIvYJYEjQTPNVMd3QZqZyF1Vyt kSArZSm2K7kE918ztZ+xGO0Mbb7fiHPJZ4mgHH0jM2hmZAxBFx3/UHSAmLtJwjUAvH Gh1ceJjB41Ywg== From: Kalle Valo To: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= Cc: Gregory Greenman , Emmanuel Grumbach , Ayala Beker , linux-wireless@vger.kernel.org Subject: Re: [PATCH] iwlwifi: Mark IWLMEI as broken 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") References: <20220907134450.1183045-1-toke@toke.dk> <87k06daysx.fsf@kernel.org> <87o7vpcbbo.fsf@toke.dk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) Date: Fri, 09 Sep 2022 12:10:08 +0300 Message-ID: <87o7vo9amn.fsf@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Toke H=C3=B8iland-J=C3=B8rgensen writes: > Kalle Valo writes: > >> Toke H=C3=B8iland-J=C3=B8rgensen writes: >> >>> forthcoming. Since just disabling the iwlmei driver works as a workarou= nd, >>> let's mark the config option as broken until it can be fixed properly. >>> >>> [0] https://bugzilla.kernel.org/show_bug.cgi?id=3D215937 >> >> 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. --=20 https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatc= hes