From: "Raghavendra, Vignesh" <vigneshr@ti.com>
To: Pratyush Yadav <pratyush@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
"Darrick J. Wong" <djwong@kernel.org>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
<linux-um@lists.infradead.org>, <linux-media@vger.kernel.org>,
<linux-mtd@lists.infradead.org>, <linux-xfs@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<linux-phy@lists.infradead.org>, <sparclinux@vger.kernel.org>
Subject: Re: Build regressions/improvements in v6.4-rc1
Date: Mon, 8 May 2023 21:16:56 +0530 [thread overview]
Message-ID: <a80f540a-492a-0585-9ed1-de3397535e07@ti.com> (raw)
In-Reply-To: <mafs035466ebk.fsf@amazon.de>
On 5/8/2023 8:49 PM, Pratyush Yadav wrote:
> On Mon, May 08 2023, Geert Uytterhoeven wrote:
>
>> On Mon, 8 May 2023, Geert Uytterhoeven wrote:
>>> Below is the list of build error/warning regressions/improvements in
>>> v6.4-rc1[1] compared to v6.3[2].
>>>
>>> Summarized:
>>> - build errors: +9/-16
>>> - build warnings: +1/-1439
>>>
>>> Happy fixing! ;-)
>>>
>>> Thanks to the linux-next team for providing the build service.
>>>
>>> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/ac9a78681b921877518763ba0e89202254349d1b/ (all 152 configs)
>>> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/457391b0380335d5e9a5babdec90ac53928b23b4/ (all 152 configs)
>>>
>>>
> [...]
>>
>>> + /kisskb/src/drivers/mtd/spi-nor/spansion.c: error: 'op' is used uninitialized [-Werror=uninitialized]: => 495:27, 364:27
>
> Hmm, I don't get why we get this warning. Line 495 is in
> s25fs256t_post_bfpt_fixup(). It declares 'op' and then it does
>
> op = (struct spi_mem_op)
> CYPRESS_NOR_RD_ANY_REG_OP(nor->params->addr_mode_nbytes,
> SPINOR_REG_CYPRESS_ARCFN, 1,
> nor->bouncebuf);
> ret = spi_nor_read_any_reg(nor, &op, nor->reg_proto);
>
Not all the fields of struct get initialized if you assign later on in
the function vs at the time of declaration... For example cmd.dtr isn't
explicitly set to any value here and may have garbage?
>
> which initializes 'op' before using it. Same with line 364 which is in
> the function cypress_nor_set_addr_mode_nbytes().
>
> Even the compiler warnings [0] don't seem to make much sense to me:
>
> /kisskb/src/drivers/mtd/spi-nor/spansion.c: In function 's25fs256t_post_bfpt_fixup':
> /kisskb/src/drivers/mtd/spi-nor/spansion.c:495:27: error: 'op' is used uninitialized [-Werror=uninitialized]
> 495 | struct spi_mem_op op;
> | ^~
> /kisskb/src/drivers/mtd/spi-nor/spansion.c:495:27: note: 'op' declared here
> 495 | struct spi_mem_op op;
> | ^~
>
> [0] http://kisskb.ellerman.id.au/kisskb/buildresult/14922057/
>
>>
>> um-x86_64-gcc12/um-allyesconfig
>>
> [...]
>
next prev parent reply other threads:[~2023-05-08 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 21:18 Linux 6.4-rc1 Linus Torvalds
2023-05-08 11:57 ` Build regressions/improvements in v6.4-rc1 Geert Uytterhoeven
2023-05-08 12:14 ` Geert Uytterhoeven
2023-05-08 15:19 ` Pratyush Yadav
2023-05-08 15:32 ` Geert Uytterhoeven
2023-05-08 15:46 ` Raghavendra, Vignesh [this message]
2023-05-09 19:25 ` [PATCH 1/2] mtd: spi-nor: spansion: make sure local struct does not contain garbage Tudor Ambarus
2023-05-09 19:25 ` [PATCH 2/2] " Tudor Ambarus
2023-05-09 19:30 ` Tudor Ambarus
2023-05-09 19:39 ` [PATCH v2] " Tudor Ambarus
2023-05-17 7:17 ` Tudor Ambarus
2023-05-22 15:58 ` Miquel Raynal
2023-05-08 20:34 ` Linux 6.4-rc1 Guenter Roeck
2023-05-10 4:31 ` linux-next stats (Was: Linux 6.4-rc1) Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a80f540a-492a-0585-9ed1-de3397535e07@ti.com \
--to=vigneshr@ti.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=chunkuang.hu@kernel.org \
--cc=davem@davemloft.net \
--cc=djwong@kernel.org \
--cc=geert@linux-m68k.org \
--cc=johannes@sipsolutions.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-um@lists.infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=sparclinux@vger.kernel.org \
--cc=tudor.ambarus@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®