From: Thierry Reding <thierry.reding@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Boris Brezillon <boris.brezillon@collabora.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the nand tree
Date: Wed, 29 Apr 2026 12:07:50 +0200 [thread overview]
Message-ID: <20260429100752.3983097-1-thierry.reding@kernel.org> (raw)
Hi all,
After merging the nand tree, today's linux-next build (all of them)
failed like this:
/srv/kbuild/next/linux.git/drivers/spi/spi-airoha-snfi.c: In function 'airoha_snand_dirmap_create':
/srv/kbuild/next/linux.git/drivers/spi/spi-airoha-snfi.c:549:50: error: passing argument 2 of 'airoha_snand_supports_op' from incompatible pointer type [-Wincompatible-pointer-types]
549 | if (!airoha_snand_supports_op(desc->mem, &desc->info.op_tmpl))
| ^~~~~~~~~~~~~~~~~~~
| |
| struct spi_mem_op **
/srv/kbuild/next/linux.git/drivers/spi/spi-airoha-snfi.c:519:63: note: expected 'const struct spi_mem_op *' but argument is of type 'struct spi_mem_op **'
519 | const struct spi_mem_op *op)
| ~~~~~~~~~~~~~~~~~~~~~~~~~^~
/srv/kbuild/next/linux.git/drivers/spi/spi-airoha-snfi.c: In function 'airoha_snand_dirmap_read':
/srv/kbuild/next/linux.git/drivers/spi/spi-airoha-snfi.c:575:36: error: 'desc->info.op_tmpl' is a pointer; did you mean to use '->'?
575 | opcode = desc->info.op_tmpl.cmd.opcode;
| ^
| ->
/srv/kbuild/next/linux.git/drivers/spi/spi-airoha-snfi.c: In function 'airoha_snand_dirmap_write':
/srv/kbuild/next/linux.git/drivers/spi/spi-airoha-snfi.c:764:36: error: 'desc->info.op_tmpl' is a pointer; did you mean to use '->'?
764 | opcode = desc->info.op_tmpl.cmd.opcode;
| ^
| ->
Caused by commit
56b2c0848273 ("spi: spi-mem: Transform the read operation template")
I'm going to roll this back and revert to yesterday's tree.
Thanks,
Thierry
next reply other threads:[~2026-04-29 10:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 10:07 Thierry Reding [this message]
2026-04-29 17:47 ` linux-next: build failure after merge of the nand tree Miquel Raynal
-- strict thread matches above, loose matches on Subject: below --
2025-03-04 2:28 Stephen Rothwell
2025-03-04 10:57 ` Miquel Raynal
2025-01-16 2:20 Stephen Rothwell
2025-01-17 2:23 ` Stephen Rothwell
2025-01-17 8:25 ` Miquel Raynal
2025-01-06 1:48 Stephen Rothwell
2025-01-06 1:51 ` Stephen Rothwell
2025-01-06 6:16 ` Md Sadre Alam
2025-01-06 13:23 ` Md Sadre Alam
2025-01-07 1:46 ` Stephen Rothwell
2023-08-21 2:02 Stephen Rothwell
2023-08-21 5:44 ` Md Sadre Alam
2022-09-21 1:32 Stephen Rothwell
2020-12-08 2:14 Stephen Rothwell
2020-09-14 1:45 Stephen Rothwell
2020-09-14 9:50 ` Alex Dewar
2020-09-14 10:58 ` Miquel Raynal
2020-09-08 3:35 Stephen Rothwell
2020-09-10 4:12 ` Stephen Rothwell
2020-09-11 16:58 ` Miquel Raynal
2020-05-25 10:45 Stephen Rothwell
2020-05-25 11:54 ` Miquel Raynal
2020-05-12 4:08 Stephen Rothwell
2020-05-12 7:04 ` Miquel Raynal
2020-03-11 2:16 Stephen Rothwell
2020-03-11 10:10 ` Miquel Raynal
2020-03-11 14:01 ` Boris Brezillon
2020-03-11 19:20 ` Janusz Krzysztofik
2019-04-01 23:14 Stephen Rothwell
2019-04-01 23:31 ` Paul Cercueil
2019-04-02 7:27 ` Miquel Raynal
2019-04-02 9:21 ` Miquel Raynal
2019-04-02 11:56 ` Miquel Raynal
2019-04-02 12:00 ` Paul Cercueil
2019-04-02 12:16 ` Miquel Raynal
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=20260429100752.3983097-1-thierry.reding@kernel.org \
--to=thierry.reding@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
/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