From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/1] [RFC] wakeup_reason: Add infrastructure to log and report why the system resumed from suspend.
Date: Fri, 28 Jan 2022 14:56:10 +0800 [thread overview]
Message-ID: <202201281421.yoAJA4z1-lkp@intel.com> (raw)
In-Reply-To: <20220128045522.3505336-1-zichar.zhang@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 4345 bytes --]
Hi Zichar,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on linux/master linus/master v5.17-rc1 next-20220127]
[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/Zichar-Zhang/wakeup_reason-Add-infrastructure-to-log-and-report-why-the-system-resumed-from-suspend/20220128-125627
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20220128/202201281421.yoAJA4z1-lkp(a)intel.com/config)
compiler: riscv64-linux-gcc (GCC) 11.2.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/b932c9637e3e3a14497ff60caedfc67608d93c13
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Zichar-Zhang/wakeup_reason-Add-infrastructure-to-log-and-report-why-the-system-resumed-from-suspend/20220128-125627
git checkout b932c9637e3e3a14497ff60caedfc67608d93c13
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=riscv SHELL=/bin/bash kernel/
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 >>):
In file included from kernel/power/main.c:19:
>> include/linux/wakeup_reason.h:29:9: warning: no previous prototype for 'log_ws_wakeup_reason' [-Wmissing-prototypes]
29 | ssize_t log_ws_wakeup_reason(void) { }
| ^~~~~~~~~~~~~~~~~~~~
>> include/linux/wakeup_reason.h:30:9: warning: no previous prototype for 'log_irq_wakeup_reason' [-Wmissing-prototypes]
30 | ssize_t log_irq_wakeup_reason(unsigned int irq_number) { }
| ^~~~~~~~~~~~~~~~~~~~~
>> include/linux/wakeup_reason.h:31:6: warning: no previous prototype for 'clear_wakeup_reason' [-Wmissing-prototypes]
31 | void clear_wakeup_reason(void) { }
| ^~~~~~~~~~~~~~~~~~~
>> include/linux/wakeup_reason.h:32:9: warning: no previous prototype for 'last_wakeup_reason_get' [-Wmissing-prototypes]
32 | ssize_t last_wakeup_reason_get(char *buf, ssize_t max) { }
| ^~~~~~~~~~~~~~~~~~~~~~
include/linux/wakeup_reason.h: In function 'log_ws_wakeup_reason':
include/linux/wakeup_reason.h:29:38: error: control reaches end of non-void function [-Werror=return-type]
29 | ssize_t log_ws_wakeup_reason(void) { }
| ^
include/linux/wakeup_reason.h: In function 'log_irq_wakeup_reason':
include/linux/wakeup_reason.h:30:58: error: control reaches end of non-void function [-Werror=return-type]
30 | ssize_t log_irq_wakeup_reason(unsigned int irq_number) { }
| ^
include/linux/wakeup_reason.h: In function 'last_wakeup_reason_get':
include/linux/wakeup_reason.h:32:58: error: control reaches end of non-void function [-Werror=return-type]
32 | ssize_t last_wakeup_reason_get(char *buf, ssize_t max) { }
| ^
cc1: some warnings being treated as errors
vim +/log_ws_wakeup_reason +29 include/linux/wakeup_reason.h
22
23 #ifdef CONFIG_SUSPEND
24 ssize_t log_ws_wakeup_reason(void);
25 ssize_t log_irq_wakeup_reason(unsigned int irq_number);
26 void clear_wakeup_reason(void);
27 ssize_t last_wakeup_reason_get(char *buf, ssize_t max);
28 #else
> 29 ssize_t log_ws_wakeup_reason(void) { }
> 30 ssize_t log_irq_wakeup_reason(unsigned int irq_number) { }
> 31 void clear_wakeup_reason(void) { }
> 32 ssize_t last_wakeup_reason_get(char *buf, ssize_t max) { }
33 #endif
34
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2022-01-28 6:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 18:49 [RFC] PM: suspend: Upstreaming wakeup reason capture support Kelly Rossmoyer
2022-01-24 17:37 ` John Stultz
2022-01-26 5:09 ` Zichar Zhang
2022-01-28 4:55 ` [PATCH 1/1] [RFC] wakeup_reason: Add infrastructure to log and report why the system resumed from suspend Zichar Zhang
2022-01-28 6:56 ` kernel test robot [this message]
2022-01-28 7:01 ` Greg KH
2022-01-28 8:43 ` Zichar Zhang
2022-01-28 8:45 ` kernel test robot
2022-01-28 8:45 ` kernel test robot
2022-01-28 9:32 ` Lee Jones
2022-01-29 7:52 ` [RFC] PM: suspend: Upstreaming wakeup reason capture support Kelly Rossmoyer
2022-01-27 19:54 ` Rafael J. Wysocki
2022-01-27 20:10 ` Rafael J. Wysocki
2022-01-29 8:26 ` Kelly Rossmoyer
2022-01-30 14:46 ` Rafael J. Wysocki
2022-02-02 7:59 ` Kelly Rossmoyer
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=202201281421.yoAJA4z1-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.