From: kbuild test robot <lkp@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: kbuild-all@lists.01.org, linux-acpi@vger.kernel.org,
devel@acpica.org, linux-pm@vger.kernel.org
Subject: [pm:pm-sleep-core 3/3] drivers/base/power/main.c:582:3: error: 'state' undeclared; did you mean 'statx'?
Date: Sun, 5 Apr 2020 19:34:37 +0800 [thread overview]
Message-ID: <202004051933.OTMBppfJ%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4252 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-sleep-core
head: 3aa654e1e731ad8f8aff1a937e09fae14380b6e5
commit: 3aa654e1e731ad8f8aff1a937e09fae14380b6e5 [3/3] PM: sleep: core: Do not skip callbacks in the resume phase
config: x86_64-defconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
git checkout 3aa654e1e731ad8f8aff1a937e09fae14380b6e5
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
drivers/base/power/main.c: In function 'dev_pm_may_skip_resume':
>> drivers/base/power/main.c:582:3: error: 'state' undeclared (first use in this function); did you mean 'statx'?
state.event == PM_EVENT_THAW);
^~~~~
statx
drivers/base/power/main.c:582:3: note: each undeclared identifier is reported only once for each function it appears in
In file included from include/linux/compiler_types.h:68:0,
from <command-line>:0:
drivers/base/power/main.c: In function 'device_resume_noirq':
drivers/base/power/main.c:597:31: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
const char uninitialized_var(*info);
^
include/linux/compiler-gcc.h:65:34: note: in definition of macro 'uninitialized_var'
#define uninitialized_var(x) x = x
^
drivers/base/power/main.c: In function 'device_resume_early':
drivers/base/power/main.c:765:31: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
const char uninitialized_var(*info);
^
include/linux/compiler-gcc.h:65:34: note: in definition of macro 'uninitialized_var'
#define uninitialized_var(x) x = x
^
drivers/base/power/main.c: In function '__device_suspend_noirq':
drivers/base/power/main.c:1192:31: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
const char uninitialized_var(*info);
^
include/linux/compiler-gcc.h:65:34: note: in definition of macro 'uninitialized_var'
#define uninitialized_var(x) x = x
^
drivers/base/power/main.c: In function '__device_suspend_late':
drivers/base/power/main.c:1377:31: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
const char uninitialized_var(*info);
^
include/linux/compiler-gcc.h:65:34: note: in definition of macro 'uninitialized_var'
#define uninitialized_var(x) x = x
^
drivers/base/power/main.c: In function 'dev_pm_may_skip_resume':
>> drivers/base/power/main.c:583:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
vim +582 drivers/base/power/main.c
563
564 /**
565 * dev_pm_may_skip_resume - System-wide device resume optimization check.
566 * @dev: Target device.
567 *
568 * Driver-level resume callbacks can be skipped for @dev if its configuration is
569 * suitable for that (power.must_resume is not set) and the current transition
570 * is not the hibernation-related "restore" one (in which case all devices must
571 * be resumed) or the current transition is hibernation-related "thaw" one and
572 * the driver-level callbacks were skipped for @dev during the corresponding
573 * "freeze" transition (which happens when DPM_FLAG_SMART_SUSPEND is set and the
574 * device remains in runtime suspend), so running the "thaw" callbacks for it
575 * may be invalid.
576 */
577 bool dev_pm_may_skip_resume(struct device *dev)
578 {
579 return (!dev->power.must_resume &&
580 pm_transition.event != PM_EVENT_RESTORE) ||
581 (dev_pm_smart_suspend_and_suspended(dev) &&
> 582 state.event == PM_EVENT_THAW);
> 583 }
584
---
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: 29061 bytes --]
reply other threads:[~2020-04-05 11:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202004051933.OTMBppfJ%lkp@intel.com \
--to=lkp@intel.com \
--cc=devel@acpica.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).