From: kbuild test robot <lkp@intel.com>
To: Chris Metcalf <cmetcalf@mellanox.com>
Cc: kbuild-all@01.org, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Chris Metcalf <cmetcalf@mellanox.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Thierry Reding <treding@nvidia.com>, Nishanth Menon <nm@ti.com>,
Jean Delvare <jdelvare@suse.de>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: [PATCH] firmware: bluefield: add boot control driver
Date: Thu, 12 Oct 2017 07:49:21 +0800 [thread overview]
Message-ID: <201710120701.QJQaTHcQ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1507569397-25656-1-git-send-email-cmetcalf@mellanox.com>
[-- Attachment #1: Type: text/plain, Size: 4274 bytes --]
Hi Chris,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.14-rc4 next-20171009]
[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/Chris-Metcalf/firmware-bluefield-add-boot-control-driver/20171012-023624
config: arm64-allmodconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
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
make.cross ARCH=arm64
All error/warnings (new ones prefixed by >>):
>> drivers/firmware/mlx-bootctl.c:146:21: error: expected ')' before numeric constant
DRIVER_ATTR(_name, 0600, _name##_show, _name##_store)
^
>> drivers/firmware/mlx-bootctl.c:148:8: note: in expansion of macro 'MBC_DRV_ATTR'
static MBC_DRV_ATTR(post_reset_wdog);
^~~~~~~~~~~~
>> drivers/firmware/mlx-bootctl.c:146:21: error: expected ')' before numeric constant
DRIVER_ATTR(_name, 0600, _name##_show, _name##_store)
^
drivers/firmware/mlx-bootctl.c:149:8: note: in expansion of macro 'MBC_DRV_ATTR'
static MBC_DRV_ATTR(reset_action);
^~~~~~~~~~~~
>> drivers/firmware/mlx-bootctl.c:146:21: error: expected ')' before numeric constant
DRIVER_ATTR(_name, 0600, _name##_show, _name##_store)
^
drivers/firmware/mlx-bootctl.c:150:8: note: in expansion of macro 'MBC_DRV_ATTR'
static MBC_DRV_ATTR(second_reset_action);
^~~~~~~~~~~~
>> drivers/firmware/mlx-bootctl.c:153:3: error: 'driver_attr_post_reset_wdog' undeclared here (not in a function)
&driver_attr_post_reset_wdog.attr,
^~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/firmware/mlx-bootctl.c:154:3: error: 'driver_attr_reset_action' undeclared here (not in a function)
&driver_attr_reset_action.attr,
^~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/firmware/mlx-bootctl.c:155:3: error: 'driver_attr_second_reset_action' undeclared here (not in a function)
&driver_attr_second_reset_action.attr,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/firmware/mlx-bootctl.c:131:16: warning: 'second_reset_action_store' defined but not used [-Wunused-function]
static ssize_t second_reset_action_store(struct device_driver *drv,
^~~~~~~~~~~~~~~~~~~~~~~~~
drivers/firmware/mlx-bootctl.c:124:16: warning: 'second_reset_action_show' defined but not used [-Wunused-function]
static ssize_t second_reset_action_show(struct device_driver *drv,
^~~~~~~~~~~~~~~~~~~~~~~~
drivers/firmware/mlx-bootctl.c:110:16: warning: 'reset_action_store' defined but not used [-Wunused-function]
static ssize_t reset_action_store(struct device_driver *drv,
^~~~~~~~~~~~~~~~~~
drivers/firmware/mlx-bootctl.c:103:16: warning: 'reset_action_show' defined but not used [-Wunused-function]
static ssize_t reset_action_show(struct device_driver *drv,
^~~~~~~~~~~~~~~~~
drivers/firmware/mlx-bootctl.c:87:16: warning: 'post_reset_wdog_store' defined but not used [-Wunused-function]
static ssize_t post_reset_wdog_store(struct device_driver *drv,
^~~~~~~~~~~~~~~~~~~~~
drivers/firmware/mlx-bootctl.c:81:16: warning: 'post_reset_wdog_show' defined but not used [-Wunused-function]
static ssize_t post_reset_wdog_show(struct device_driver *drv,
^~~~~~~~~~~~~~~~~~~~
vim +146 drivers/firmware/mlx-bootctl.c
144
145 #define MBC_DRV_ATTR(_name) \
> 146 DRIVER_ATTR(_name, 0600, _name##_show, _name##_store)
147
> 148 static MBC_DRV_ATTR(post_reset_wdog);
> 149 static MBC_DRV_ATTR(reset_action);
> 150 static MBC_DRV_ATTR(second_reset_action);
151
152 static struct attribute *mbc_dev_attrs[] = {
> 153 &driver_attr_post_reset_wdog.attr,
> 154 &driver_attr_reset_action.attr,
> 155 &driver_attr_second_reset_action.attr,
156 NULL
157 };
158
---
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: 57569 bytes --]
prev parent reply other threads:[~2017-10-11 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 17:16 [PATCH] firmware: bluefield: add boot control driver Chris Metcalf
2017-10-10 10:15 ` Sudeep Holla
2017-10-10 10:23 ` Mark Rutland
2017-10-10 11:30 ` Ard Biesheuvel
2017-10-10 11:58 ` Leif Lindholm
2017-10-10 12:23 ` Grant Likely
2017-10-11 23:49 ` kbuild 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=201710120701.QJQaTHcQ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=cmetcalf@mellanox.com \
--cc=jdelvare@suse.de \
--cc=kbuild-all@01.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mingo@kernel.org \
--cc=nm@ti.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sudeep.holla@arm.com \
--cc=treding@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.