All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC v2] cpuidle : Add support for pseudo-cpuidle driver
Date: Wed, 23 Sep 2020 01:58:56 +0800	[thread overview]
Message-ID: <202009230136.vvcPtev4%lkp@intel.com> (raw)
In-Reply-To: <20200921063951.131529-1-huntbag@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 3420 bytes --]

Hi Abhishek,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on pm/linux-next]
[also build test WARNING on linux/master linus/master v5.9-rc6 next-20200921]
[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/Abhishek-Goel/cpuidle-Add-support-for-pseudo-cpuidle-driver/20200921-144126
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

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 >>):

   drivers/cpuidle/cpuidle-test.c: In function 'add_cpuidle_states':
>> drivers/cpuidle/cpuidle-test.c:184:6: warning: variable 'rc' set but not used [-Wunused-but-set-variable]
     184 |  int rc;
         |      ^~

# https://github.com/0day-ci/linux/commit/d9e8ba5bf4c4223e99414f48d2049131f045551d
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Abhishek-Goel/cpuidle-Add-support-for-pseudo-cpuidle-driver/20200921-144126
git checkout d9e8ba5bf4c4223e99414f48d2049131f045551d
vim +/rc +184 drivers/cpuidle/cpuidle-test.c

   172	
   173	static int add_cpuidle_states(void)
   174	{
   175		/* Parse the module param and initialize the idle states here
   176		 * in cpuidle_state_table.
   177		 */
   178		char *this_param;
   179		char *input_name = name;
   180		char *input_res = residency_us;
   181		char *input_lat = latency_us;
   182		int index = 1;
   183		long temp;
 > 184		int rc;
   185	
   186		switch (sim_type) {
   187		case 1:
   188			cpuidle_state_table = cpuidle_states_ppc;
   189			return 0;
   190		case 2:
   191			cpuidle_state_table = cpuidle_states_intel;
   192			return 0;
   193		case 3:
   194			break;
   195		default:
   196			pr_warn("Sim value out of bound\n");
   197			break;
   198		}
   199	
   200		if (strnlen(input_name, MAX_PARAM_LENGTH)) {
   201			while ((this_param = strsep(&input_name, ",")) && index <= nr_states) {
   202				strcpy(cpuidle_states[index].name, this_param);
   203				cpuidle_states[index].enter = idle_loop;
   204				index++;
   205			}
   206		}
   207	
   208		if (strnlen(input_res, MAX_PARAM_LENGTH)) {
   209			index = 1;
   210			while ((this_param = strsep(&input_res, ",")) && index <= nr_states) {
   211				rc = kstrtol(this_param, 10, &temp);
   212				cpuidle_states[index].target_residency = temp;
   213				index++;
   214			}
   215		}
   216	
   217		if (strnlen(input_lat, MAX_PARAM_LENGTH)) {
   218			index = 1;
   219			while ((this_param = strsep(&input_lat, ",")) && index <= nr_states) {
   220				rc = kstrtol(this_param, 10, &temp);
   221				cpuidle_states[index].exit_latency = temp;
   222				index++;
   223			}
   224		}
   225	
   226		cpuidle_state_table = cpuidle_states;
   227		return nr_states;
   228	}
   229	

---
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: 74715 bytes --]

      reply	other threads:[~2020-09-22 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  6:39 [RFC v2] cpuidle : Add support for pseudo-cpuidle driver Abhishek Goel
2020-09-22 17:58 ` kernel test robot [this message]

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=202009230136.vvcPtev4%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.