Return-path: Received: from mail-oi0-f67.google.com ([209.85.218.67]:36317 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757125AbdETCXC (ORCPT ); Fri, 19 May 2017 22:23:02 -0400 Subject: Re: [PATCH] rtlwifi: btcoex: 23b 1ant: initialize bt_disabled to false To: Dan Carpenter Cc: Chaoming Li , Kalle Valo , Ping-Ke Shih , Yan-Hsuan Chuang , linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org References: <20170519212539.cihnvwl7irchxoaj@mwanda> From: Larry Finger Message-ID: (sfid-20170520_042417_587372_4D68AD77) Date: Fri, 19 May 2017 21:22:59 -0500 MIME-Version: 1.0 In-Reply-To: <20170519212539.cihnvwl7irchxoaj@mwanda> Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 05/19/2017 04:25 PM, Dan Carpenter wrote: > We only want to disable this if bt_disable_cnt is >= 2. > > Fixes: f66509e3d7c2 ("rtlwifi: btcoex: Remove 23b 1ant configuration parameter") > Signed-off-by: Dan Carpenter > --- > Btw, that patch also introduced Sparse warning but I don't know how to > address it. > > drivers/net/wireless/realtek/rtlwifi/btcoexist/halbtc8723b1ant.c:1432:63: warning: odd constant _Bool cast (2 becomes 1) I agree that bt_disabled needs to be initialized. Actually, I would have expected an unitialized variable warning out of gcc. Earlier today, I finished applying the rest of the btcoex patches from Realtek and now have a clean Sparse run. I never saw that message, and I certainly do not understand it either. Larry