From mboxrd@z Thu Jan 1 00:00:00 1970 From: kvalo@codeaurora.org (Kalle Valo) Date: Fri, 31 Aug 2018 15:52:48 +0000 (UTC) Subject: [PATCH] mt76: Fix comparisons with invalid hardware key index In-Reply-To: <20180823212738.18431-1-geert@linux-m68k.org> References: <20180823212738.18431-1-geert@linux-m68k.org> Message-ID: <20180831155248.D7F8D607F7@smtp.codeaurora.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Geert Uytterhoeven wrote: > With gcc 4.1.2: > > drivers/net/wireless/mediatek/mt76/mt76x0/tx.c: In function ?mt76x0_tx?: > drivers/net/wireless/mediatek/mt76/mt76x0/tx.c:169: warning: comparison is always true due to limited range of data type > drivers/net/wireless/mediatek/mt76/mt76x2_tx_common.c: In function ?mt76x2_tx?: > drivers/net/wireless/mediatek/mt76/mt76x2_tx_common.c:35: warning: comparison is always true due to limited range of data type > > While assigning -1 to a u8 works fine, comparing with -1 does not work > as expected. > > Fix this by comparing with 0xff, like is already done in some other > places. > > Signed-off-by: Geert Uytterhoeven Patch applied to wireless-drivers-next.git, thanks. 81c8eccc2404 mt76: Fix comparisons with invalid hardware key index -- https://patchwork.kernel.org/patch/10574583/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches