From: kbuild test robot <lkp@intel.com>
To: richard.gong@linux.intel.com
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
robh+dt@kernel.org, mark.rutland@arm.com, dinguyen@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
sen.li@intel.com, richard.gong@intel.com
Subject: Re: [PATCHv5 2/4] firmware: add Intel Stratix10 remote system update driver
Date: Wed, 4 Sep 2019 11:25:02 +0800 [thread overview]
Message-ID: <201909041122.qPwVj0cp%lkp@intel.com> (raw)
In-Reply-To: <1567516701-26026-3-git-send-email-richard.gong@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3-rc7 next-20190903]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/richard-gong-linux-intel-com/add-Intel-Stratix10-remote-system-update-driver/20190904-072434
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/firmware/stratix10-rsu.c:443:4: error: 'struct device_driver' has no member named 'dev_groups'; did you mean 'groups'?
.dev_groups = rsu_groups,
^~~~~~~~~~
groups
>> drivers/firmware/stratix10-rsu.c:443:17: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.dev_groups = rsu_groups,
^~~~~~~~~~
drivers/firmware/stratix10-rsu.c:443:17: note: (near initialization for 'stratix10_rsu_driver.driver.bus')
cc1: some warnings being treated as errors
vim +443 drivers/firmware/stratix10-rsu.c
437
438 static struct platform_driver stratix10_rsu_driver = {
439 .probe = stratix10_rsu_probe,
440 .remove = stratix10_rsu_remove,
441 .driver = {
442 .name = "stratix10-rsu",
> 443 .dev_groups = rsu_groups,
444 },
445 };
446
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 66447 bytes --]
next prev parent reply other threads:[~2019-09-04 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 13:18 [PATCHv5 0/4] " richard.gong
2019-09-03 13:18 ` [PATCHv5 1/4] firmware: stratix10-svc: extend svc to support new RSU features richard.gong
2019-09-03 13:18 ` [PATCHv5 2/4] firmware: add Intel Stratix10 remote system update driver richard.gong
2019-09-04 3:25 ` kbuild test robot [this message]
2019-09-03 13:18 ` [PATCHv5 3/4] firmware: rsu: document sysfs interface richard.gong
2019-09-03 13:18 ` [PATCHv5 4/4] MAINTAINERS: add maintainer for Intel Stratix10 FW drivers richard.gong
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=201909041122.qPwVj0cp%lkp@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=richard.gong@intel.com \
--cc=richard.gong@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=sen.li@intel.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
all inboxes | Powered by JetHome®