From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kalle Valo Subject: Re: [PATCH 3/3] iwlwifi: Load firmware exclusively for Intel WiFi Date: Wed, 03 Oct 2018 11:58:12 +0300 Message-ID: <87bm8bjtjv.fsf@kamboji.qca.qualcomm.com> References: <20181003071513.13004-3-kai.heng.feng@canonical.com> <2787bccf20b6f647de9f4cafae5fd223e771b167.camel@intel.com> Mime-Version: 1.0 Content-Type: text/plain Cc: Kai-Heng Feng , linux-kernel@vger.kernel.org, Johannes Berg , Emmanuel Grumbach , Intel Linux Wireless , "David S. Miller" , linux-wireless@vger.kernel.org, netdev@vger.kernel.org To: Luciano Coelho Return-path: In-Reply-To: <2787bccf20b6f647de9f4cafae5fd223e771b167.camel@intel.com> (Luciano Coelho's message of "Wed, 03 Oct 2018 10:24:44 +0300") Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Luciano Coelho writes: >> +#if IS_ENABLED(CONFIG_BT_INTEL) >> + if (firmware_unlock_func) { >> + firmware_unlock_func(); >> + symbol_put(btintel_firmware_lock); >> + firmware_lock_func = NULL; >> + symbol_put(btintel_firmware_unlock); >> + firmware_unlock_func = NULL; >> + } >> +#endif >> + } >> else >> ret = iwl_pcie_load_given_ucode(trans, fw); >> > > I'm not sure I like adding this BT-specific stuff here, especially not > without a detailed explanation. This looks like an ugly hack and the commit log tells nothing. This really needs strong justifications to even consider doing something like this. -- Kalle Valo