From: kernel test robot <lkp@intel.com>
To: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Furquan Shaikh <furquan@chromium.org>
Subject: [jsarha:topic/cros-sof-v4.14-rebase 199/9999] drivers/idle/intel_idle.c:1000:72: sparse: sparse: incompatible types in conditional expression (different base types):
Date: Sun, 24 Jul 2022 12:38:20 +0800 [thread overview]
Message-ID: <202207241232.utAadQDp-lkp@intel.com> (raw)
tree: https://github.com/jsarha/linux topic/cros-sof-v4.14-rebase
head: 18a233f3f676a98dde00947535d99ab1a54da340
commit: 984b012fc9b1fc849276848135307edabd0d5a58 [199/9999] CHROMIUM: intel_idle: dump debug info when S0ix fails
config: i386-randconfig-s003 (https://download.01.org/0day-ci/archive/20220724/202207241232.utAadQDp-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/jsarha/linux/commit/984b012fc9b1fc849276848135307edabd0d5a58
git remote add jsarha https://github.com/jsarha/linux
git fetch --no-tags jsarha topic/cros-sof-v4.14-rebase
git checkout 984b012fc9b1fc849276848135307edabd0d5a58
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/idle/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/idle/intel_idle.c:1000:72: sparse: sparse: incompatible types in conditional expression (different base types):
>> drivers/idle/intel_idle.c:1000:72: sparse: int
>> drivers/idle/intel_idle.c:1000:72: sparse: void
vim +1000 drivers/idle/intel_idle.c
988
989 static int check_slp_s0(u64 slp_s0_saved_count)
990 {
991 u64 slp_s0_new_count;
992
993 if (get_slpS0_count(&slp_s0_new_count)) {
994 pr_warn("After s2idle attempt: Unable to read SLP S0 residency counter\n");
995 return -EIO;
996 }
997
998 if (slp_s0_saved_count == slp_s0_new_count) {
999 WARN(1, "CPU did not enter SLP S0 for suspend-to-idle.\n");
> 1000 boot_cpu_data.x86_model == INTEL_FAM6_ATOM_GEMINI_LAKE ?
1001 telem_soc_states_display() : pmc_core_ppfear_display();
1002 return -EIO;
1003 }
1004
1005 return 0;
1006 }
1007
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-24 4:38 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=202207241232.utAadQDp-lkp@intel.com \
--to=lkp@intel.com \
--cc=furquan@chromium.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajneesh.bhardwaj@intel.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®