From: kernel test robot <lkp@intel.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, suleiman@google.com,
briannorris@google.com, Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2] PM: sleep: Expose last succeeded resumed timestamp in sysfs
Date: Sat, 28 Oct 2023 19:26:10 +0800 [thread overview]
Message-ID: <202310281942.ZwkSMsVB-lkp@intel.com> (raw)
In-Reply-To: <169845668624.1319505.1097714089024984847.stgit@mhiramat.roam.corp.google.com>
Hi Masami,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.6-rc7 next-20231027]
[cannot apply to pavel-leds/for-next]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Masami-Hiramatsu-Google/PM-sleep-Expose-last-succeeded-resumed-timestamp-in-sysfs/20231028-093251
base: linus/master
patch link: https://lore.kernel.org/r/169845668624.1319505.1097714089024984847.stgit%40mhiramat.roam.corp.google.com
patch subject: [PATCH v2] PM: sleep: Expose last succeeded resumed timestamp in sysfs
config: mips-allyesconfig (https://download.01.org/0day-ci/archive/20231028/202310281942.ZwkSMsVB-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231028/202310281942.ZwkSMsVB-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310281942.ZwkSMsVB-lkp@intel.com/
All warnings (new ones prefixed by >>):
kernel/power/main.c: In function 'last_success_resume_time_show':
>> kernel/power/main.c:427:38: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 4 has type 'long int' [-Wformat=]
427 | return sprintf(buf, "%llu.%llu\n",
| ~~~^
| |
| long long unsigned int
| %lu
428 | suspend_stats.last_success_resume_time.tv_sec,
429 | suspend_stats.last_success_resume_time.tv_nsec);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| long int
kernel/power/main.c: In function 'suspend_stats_show':
kernel/power/main.c:528:62: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 4 has type 'long int' [-Wformat=]
528 | seq_printf(s, "last_success_resume_time:\t%-llu.%llu\n",
| ~~~^
| |
| long long unsigned int
| %lu
529 | suspend_stats.last_success_resume_time.tv_sec,
530 | suspend_stats.last_success_resume_time.tv_nsec);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| long int
vim +427 kernel/power/main.c
423
424 static ssize_t last_success_resume_time_show(struct kobject *kobj,
425 struct kobj_attribute *attr, char *buf)
426 {
> 427 return sprintf(buf, "%llu.%llu\n",
428 suspend_stats.last_success_resume_time.tv_sec,
429 suspend_stats.last_success_resume_time.tv_nsec);
430 }
431 static struct kobj_attribute last_success_resume_time =
432 __ATTR_RO(last_success_resume_time);
433
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-28 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 1:31 [PATCH v2] PM: sleep: Expose last succeeded resumed timestamp in sysfs Masami Hiramatsu (Google)
2023-10-28 11:26 ` kernel test robot [this message]
2023-10-28 12:37 ` Masami Hiramatsu
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=202310281942.ZwkSMsVB-lkp@intel.com \
--to=lkp@intel.com \
--cc=briannorris@google.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=suleiman@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