Re: linux-next: build warning after merge of the spi tree

From: Jean Pihet <jean.pihet@newoldbits.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Brown <broonie@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the spi tree
Date: Wed, 15 Jan 2020 10:10:09 +0100	[thread overview]
Message-ID: <CAORVsuWs=0su+y2iLfL7zUygW8UgT8WzTXoCJiyBGFp_UG8yFA@mail.gmail.com> (raw)
In-Reply-To: <20200115132325.3ac3ca0f@canb.auug.org.au>

Hi Stephen,

I did not have this warning, it may be a combination of compiler
version and build flags. Do you need a fixup patch for it?

Thanks,
Jean

On Wed, Jan 15, 2020 at 3:23 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the spi tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> drivers/spi/spi-ti-qspi.c: In function 'ti_qspi_start_transfer_one':
> drivers/spi/spi-ti-qspi.c:392:8: warning: 'rx_wlen' may be used uninitialized in this function [-Wmaybe-uninitialized]
>   392 |     if (rx_wlen >= 32)
>       |        ^
> drivers/spi/spi-ti-qspi.c:318:12: note: 'rx_wlen' was declared here
>   318 |  u8 rxlen, rx_wlen;
>       |            ^~~~~~~
>
> Introduced by commit
>
>   e7cc5cfbea4c ("spi: spi-ti-qspi: optimize byte-transfers")
>
> Looks like it may be a false positive.
>
> --
> Cheers,
> Stephen Rothwell