From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Moritz Fischer <mdf@kernel•org>, Xu Yilun <yilun.xu@intel•com>,
Wu Hao <hao.wu@intel•com>
Cc: Andy Shevchenko <andriy.shevchenko@linux•intel.com>,
Xu Yilun <yilun.xu@linux•intel.com>,
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 fpga tree
Date: Fri, 12 Apr 2024 15:11:47 +1000 [thread overview]
Message-ID: <20240412151147.22a059ff@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
Hi all,
After merging the fpga tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/fpga/ice40-spi.c:201:35: error: implicit declaration of function 'of_match_ptr' [-Werror=implicit-function-declaration]
201 | .of_match_table = of_match_ptr(ice40_fpga_of_match),
| ^~~~~~~~~~~~
drivers/fpga/ice40-spi.c:201:35: error: initialization of 'const struct of_device_id *' from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
drivers/fpga/ice40-spi.c:201:35: note: (near initialization for 'ice40_fpga_driver.driver.of_match_table')
drivers/fpga/ice40-spi.c:201:35: error: initializer element is not constant
drivers/fpga/ice40-spi.c:201:35: note: (near initialization for 'ice40_fpga_driver.driver.of_match_table')
cc1: all warnings being treated as errors
Caused by commit
5d04660b29fb ("fpga: ice40-spi: Remove unused of_gpio.h")
I have used the fpga tree from next-20240411 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-04-12 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 5:11 Stephen Rothwell [this message]
2024-04-12 15:27 ` linux-next: build failure after merge of the fpga tree Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2025-06-16 4:11 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=20240412151147.22a059ff@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andriy.shevchenko@linux$(echo .)intel.com \
--cc=hao.wu@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mdf@kernel$(echo .)org \
--cc=yilun.xu@intel$(echo .)com \
--cc=yilun.xu@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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