From: kbuild test robot <lkp@intel.com>
To: chenxiang <chenxiang66@hisilicon.com>,
rafael@kernel.org, pavel@ucw.cz, sre@kernel.org
Cc: kbuild-all@lists.01.org, john.garry@huawei.com,
linux-pm@vger.kernel.org, linuxarm@huawei.com,
Xiang Chen <chenxiang66@hisilicon.com>
Subject: Re: [PATCH] base:power:sysfs: Remove redundant attribute runtime_status in runtime_attrs
Date: Thu, 21 May 2020 21:05:42 +0800 [thread overview]
Message-ID: <202005212049.sWN89Bjc%lkp@intel.com> (raw)
In-Reply-To: <1590053147-32207-1-git-send-email-chenxiang66@hisilicon.com>
[-- Attachment #1: Type: text/plain, Size: 2291 bytes --]
Hi chenxiang,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on pm/linux-next]
[also build test WARNING on pavel-linux-leds/for-next v5.7-rc6 next-20200519]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/chenxiang/base-power-sysfs-Remove-redundant-attribute-runtime_status-in-runtime_attrs/20200521-173130
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: arm-eseries_pxa_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.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
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
In file included from drivers/base/power/sysfs.c:3:
include/linux/device.h:132:26: warning: 'dev_attr_runtime_status' defined but not used [-Wunused-variable]
132 | struct device_attribute dev_attr_##_name = __ATTR_RO(_name)
| ^~~~~~~~~
>> drivers/base/power/sysfs.c:177:8: note: in expansion of macro 'DEVICE_ATTR_RO'
177 | static DEVICE_ATTR_RO(runtime_status);
| ^~~~~~~~~~~~~~
vim +/DEVICE_ATTR_RO +177 drivers/base/power/sysfs.c
0fcb4eef829449 Alan Stern 2010-07-08 176
47acbd77e6e481 Andy Shevchenko 2017-11-10 @177 static DEVICE_ATTR_RO(runtime_status);
15bcb91d7e607d Alan Stern 2010-09-25 178
:::::: The code at line 177 was first introduced by commit
:::::: 47acbd77e6e481abf2f41d3a99cb3762f296b2e6 PM / sysfs: Convert to use DEVICE_ATTR_RO / DEVICE_ATTR_RW
:::::: TO: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
:::::: CC: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
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: 15557 bytes --]
next prev parent reply other threads:[~2020-05-21 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 9:25 [PATCH] base:power:sysfs: Remove redundant attribute runtime_status in runtime_attrs chenxiang
2020-05-21 13:05 ` kbuild test robot [this message]
2020-05-22 3:18 ` chenxiang (M)
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=202005212049.sWN89Bjc%lkp@intel.com \
--to=lkp@intel.com \
--cc=chenxiang66@hisilicon.com \
--cc=john.garry@huawei.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=sre@kernel.org \
/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).