From: kbuild test robot <lkp@intel.com>
To: RaviChandra Sadineni <ravisadineni@chromium.org>
Cc: kbuild-all@01.org, ravisadineni@chromium.org,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
linux-kernel@vger.kernel.org, tbroch@google.com,
dnojiri@google.com
Subject: Re: [PATCH V2] cros_ec: Expose sysfile to force battery cut-off on shutdown.
Date: Mon, 4 Mar 2019 22:58:58 +0800 [thread overview]
Message-ID: <201903042214.V4hyOOZp%fengguang.wu@intel.com> (raw)
In-Reply-To: <20190304005414.218310-1-ravisadineni@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]
Hi RaviChandra,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.0]
[cannot apply to next-20190301]
[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/RaviChandra-Sadineni/cros_ec-Expose-sysfile-to-force-battery-cut-off-on-shutdown/20190304-220513
config: nds32-allyesconfig (attached as .config)
compiler: nds32le-linux-gcc (GCC) 6.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=6.4.0 make.cross ARCH=nds32
All error/warnings (new ones prefixed by >>):
>> drivers/platform/chrome/cros_ec_sysfs.c:369:3: error: 'dev_attr_cutoff_battery_at_shutdown' undeclared here (not in a function)
&dev_attr_cutoff_battery_at_shutdown.attr,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/platform/chrome/cros_ec_sysfs.c:24:0:
include/linux/device.h:602:26: warning: 'dev_attr_cutoff_at_shutdown' defined but not used [-Wunused-variable]
struct device_attribute dev_attr_##_name = __ATTR_WO(_name)
^
>> drivers/platform/chrome/cros_ec_sysfs.c:366:8: note: in expansion of macro 'DEVICE_ATTR_WO'
static DEVICE_ATTR_WO(cutoff_at_shutdown);
^~~~~~~~~~~~~~
vim +/dev_attr_cutoff_battery_at_shutdown +369 drivers/platform/chrome/cros_ec_sysfs.c
361
362 static DEVICE_ATTR_RW(reboot);
363 static DEVICE_ATTR_RO(version);
364 static DEVICE_ATTR_RO(flashinfo);
365 static DEVICE_ATTR_RW(kb_wake_angle);
> 366 static DEVICE_ATTR_WO(cutoff_at_shutdown);
367
368 static struct attribute *__ec_attrs[] = {
> 369 &dev_attr_cutoff_battery_at_shutdown.attr,
370 &dev_attr_kb_wake_angle.attr,
371 &dev_attr_reboot.attr,
372 &dev_attr_version.attr,
373 &dev_attr_flashinfo.attr,
374 NULL,
375 };
376
---
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: 49917 bytes --]
next prev parent reply other threads:[~2019-03-04 14:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 19:21 [PATCH] " RaviChandra Sadineni
[not found] ` <CABXOdTdXcCeqkqcH69dG62mLmurbDOcrhhVGm6BgnBzR-1KETg@mail.gmail.com>
2019-03-04 0:54 ` [PATCH V2] " RaviChandra Sadineni
2019-03-04 14:49 ` kbuild test robot
2019-03-04 14:58 ` kbuild test robot [this message]
[not found] ` <CABXOdTdvMKGHoE5JQBLca_6V+ihRiUedgnyb2or8GraBDsKYWQ@mail.gmail.com>
2019-03-05 0:51 ` [PATCH V3] " RaviChandra Sadineni
2019-03-05 0:53 ` RaviChandra Sadineni
2019-03-07 11:56 ` Enric Balletbo i Serra
2019-03-08 0:11 ` [PATCH V4] cros_ec: Expose sysfile to force battery cutoff " RaviChandra Sadineni
2019-03-09 1:42 ` [PATCH V5] platform/chrome: mfd/cros_ec_dev: Add sysfile to force RaviChandra Sadineni
2019-03-13 17:38 ` Enric Balletbo i Serra
2019-03-09 1:46 ` [PATCH V3] cros_ec: Expose sysfile to force battery cut-off on shutdown Ravi Chandra Sadineni
2019-03-05 1:00 ` [PATCH V2] " Ravi Chandra Sadineni
[not found] ` <CAC0y+AgmxjQv5gm4Bc5mMhnX_PwrixGfraHxg+EGvZXhi2mGPg@mail.gmail.com>
2019-03-05 17:59 ` Ravi Chandra Sadineni
2019-03-04 1:02 ` [PATCH] " Ravi Chandra Sadineni
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=201903042214.V4hyOOZp%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bleung@chromium.org \
--cc=dnojiri@google.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ravisadineni@chromium.org \
--cc=tbroch@google.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®