From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id F07AA2F80 for ; Tue, 27 Apr 2021 16:08:53 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id EF63E6101E; Tue, 27 Apr 2021 16:08:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1619539733; bh=MGTdEc1hoNf5ENVvBpk9WOWNX2m5f9EvQSNbL2ciWTk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=GbfG95D5Uqnx8KHAW+8ZCOLlD33EU4leC0F8urVZg1K4UFatPOVA1dSbsG5MO29QS 0tLe9hOynswu+1GuRz++KTyokdFuc+ON7CZxpcVmBf6LmLP0mrP0Nlk36SW0u00dBO NfK/wYvFREsp91Gd4u68piAal08k2Nz5v//5fJTw= Date: Tue, 27 Apr 2021 18:08:51 +0200 From: Greg Kroah-Hartman To: Arnd Bergmann Cc: Dan Carpenter , Fabio Aiuto , Ross Schmidt , Marco Cesati , Johannes Berg , Ivan Safonov , linux-staging@lists.linux.dev, Linux Kernel Mailing List Subject: Re: [PATCH] [v2] staging: rtl8723bs: avoid bogus gcc warning Message-ID: References: <20210422152648.2891996-1-arnd@kernel.org> X-Mailing-List: linux-staging@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Tue, Apr 27, 2021 at 03:00:28PM +0200, Arnd Bergmann wrote: > On Tue, Apr 27, 2021 at 2:42 PM Greg Kroah-Hartman > wrote: > > On Tue, Apr 27, 2021 at 01:59:32PM +0200, Arnd Bergmann wrote: > > > On Tue, Apr 27, 2021 at 11:33 AM Greg Kroah-Hartman > > > wrote: > > > > > > > > > What version of gcc causes this? Should this go into 5.13-final and be > > > > backported? Or is this only showing up on "unreleased" versions of gcc > > > > and it is safe to wait until 5.14? > > > > > > As I understand, this is related to > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99673 > > > > > > gcc-11.1.0 has now been released and it produces this warning. > > > > What's the odds we can get gcc to fix their bug, as it's not a kernel > > issue? :) > > I think there is a high chance it will get fixed in gcc-11.2 or 12.1, but > anyone using gcc-11.1 will still have the problem. Ugh, ok, I'll queue it up for 5.13-final. thanks, greg k-h