From: kernel test robot <lkp@intel.com>
To: trix@redhat.com, mdf@kernel.org, hao.wu@intel.com,
michal.simek@xilinx.com
Cc: kbuild-all@lists.01.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Tom Rix <trix@redhat.com>
Subject: Re: [PATCH v2 1/5] fpga: generalize updating the card
Date: Sun, 23 May 2021 04:59:57 +0800 [thread overview]
Message-ID: <202105230441.cT6rt6Ih-lkp@intel.com> (raw)
In-Reply-To: <20210520182930.2021923-1-trix@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4656 bytes --]
Hi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linux/master]
[also build test WARNING on linus/master v5.13-rc2 next-20210521]
[cannot apply to xlnx/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/trix-redhat-com/generalize-fpga_mgr_load/20210522-224247
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git dd860052c99b1e088352bdd4fb7aef46f8d2ef47
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/808aa2625c17a6d7c5a81e9c3e45d122a5e32f0a
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review trix-redhat-com/generalize-fpga_mgr_load/20210522-224247
git checkout 808aa2625c17a6d7c5a81e9c3e45d122a5e32f0a
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/fpga/stratix10-soc.c:398:3: error: 'const struct fpga_manager_ops' has no member named 'partial_reconfig'
398 | .partial_reconfig.write_init = s10_ops_write_init,
| ^~~~~~~~~~~~~~~~
drivers/fpga/stratix10-soc.c:398:37: error: initialization of 'u64 (*)(struct fpga_manager *)' {aka 'long long unsigned int (*)(struct fpga_manager *)'} from incompatible pointer type 'int (*)(struct fpga_manager *, struct fpga_image_info *, const char *, size_t)' {aka 'int (*)(struct fpga_manager *, struct fpga_image_info *, const char *, long unsigned int)'} [-Werror=incompatible-pointer-types]
398 | .partial_reconfig.write_init = s10_ops_write_init,
| ^~~~~~~~~~~~~~~~~~
drivers/fpga/stratix10-soc.c:398:37: note: (near initialization for 's10_ops.status')
drivers/fpga/stratix10-soc.c:399:3: error: 'const struct fpga_manager_ops' has no member named 'partial_reconfig'
399 | .partial_reconfig.write = s10_ops_write,
| ^~~~~~~~~~~~~~~~
drivers/fpga/stratix10-soc.c:399:37: error: invalid initializer
399 | .partial_reconfig.write = s10_ops_write,
| ^~~~~~~~~~~~~
drivers/fpga/stratix10-soc.c:399:37: note: (near initialization for 's10_ops.reconfig.<anonymous>')
drivers/fpga/stratix10-soc.c:400:3: error: 'const struct fpga_manager_ops' has no member named 'partial_reconfig'
400 | .partial_reconfig.write_complete = s10_ops_write_complete,
| ^~~~~~~~~~~~~~~~
drivers/fpga/stratix10-soc.c:400:37: error: invalid initializer
400 | .partial_reconfig.write_complete = s10_ops_write_complete,
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/fpga/stratix10-soc.c:400:37: note: (near initialization for 's10_ops.reimage.<anonymous>')
>> drivers/fpga/stratix10-soc.c:396:48: warning: missing braces around initializer [-Wmissing-braces]
396 | static const struct fpga_manager_ops s10_ops = {
| ^
......
399 | .partial_reconfig.write = s10_ops_write,
| { }
400 | .partial_reconfig.write_complete = s10_ops_write_complete,
| {
401 | };
| }
cc1: some warnings being treated as errors
vim +396 drivers/fpga/stratix10-soc.c
e7eef1d7633a87 Alan Tull 2018-11-13 395
e7eef1d7633a87 Alan Tull 2018-11-13 @396 static const struct fpga_manager_ops s10_ops = {
e7eef1d7633a87 Alan Tull 2018-11-13 397 .state = s10_ops_state,
808aa2625c17a6 Tom Rix 2021-05-20 398 .partial_reconfig.write_init = s10_ops_write_init,
808aa2625c17a6 Tom Rix 2021-05-20 399 .partial_reconfig.write = s10_ops_write,
808aa2625c17a6 Tom Rix 2021-05-20 400 .partial_reconfig.write_complete = s10_ops_write_complete,
e7eef1d7633a87 Alan Tull 2018-11-13 401 };
e7eef1d7633a87 Alan Tull 2018-11-13 402
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 77691 bytes --]
prev parent reply other threads:[~2021-05-22 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 18:29 [PATCH v2 1/5] fpga: generalize updating the card trix
2021-05-22 19:34 ` kernel test robot
2021-05-22 20:59 ` kernel test robot [this message]
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=202105230441.cT6rt6Ih-lkp@intel.com \
--to=lkp@intel.com \
--cc=hao.wu@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=trix@redhat.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;
as well as URLs for NNTP newsgroup(s).