linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Joao Martins <joao.m.martins@oracle.com>
Cc: kbuild-all@01.org, linux-acpi@vger.kernel.org, devel@acpica.org,
	linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: [pm:bleeding-edge 175/181] drivers/cpuidle/driver.c:270:4: error: 'cpuidle_prev_governor' undeclared; did you mean 'cpuidle_find_governor'?
Date: Sat, 7 Sep 2019 00:44:22 +0800	[thread overview]
Message-ID: <201909070020.yR8k4sTf%lkp@intel.com> (raw)

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

tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
head:   79f0d67a241f0583b994c73437caa54a4e942737
commit: 73d2bcced00671c2b724a31c3a4b3401c3e278d0 [175/181] cpuidle: allow governor switch on cpuidle_register_driver()
config: arm-defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 73d2bcced00671c2b724a31c3a4b3401c3e278d0
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=arm 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/cpuidle/driver.c: In function 'cpuidle_register_driver':
>> drivers/cpuidle/driver.c:270:4: error: 'cpuidle_prev_governor' undeclared (first use in this function); did you mean 'cpuidle_find_governor'?
       cpuidle_prev_governor = cpuidle_curr_governor;
       ^~~~~~~~~~~~~~~~~~~~~
       cpuidle_find_governor
   drivers/cpuidle/driver.c:270:4: note: each undeclared identifier is reported only once for each function it appears in
   drivers/cpuidle/driver.c: In function 'cpuidle_unregister_driver':
   drivers/cpuidle/driver.c:301:6: error: 'cpuidle_prev_governor' undeclared (first use in this function); did you mean 'cpuidle_find_governor'?
     if (cpuidle_prev_governor) {
         ^~~~~~~~~~~~~~~~~~~~~
         cpuidle_find_governor

vim +270 drivers/cpuidle/driver.c

   245	
   246	/**
   247	 * cpuidle_register_driver - registers a driver
   248	 * @drv: a pointer to a valid struct cpuidle_driver
   249	 *
   250	 * Register the driver under a lock to prevent concurrent attempts to
   251	 * [un]register the driver from occuring at the same time.
   252	 *
   253	 * Returns 0 on success, a negative error code (returned by
   254	 * __cpuidle_register_driver()) otherwise.
   255	 */
   256	int cpuidle_register_driver(struct cpuidle_driver *drv)
   257	{
   258		struct cpuidle_governor *gov;
   259		int ret;
   260	
   261		spin_lock(&cpuidle_driver_lock);
   262		ret = __cpuidle_register_driver(drv);
   263		spin_unlock(&cpuidle_driver_lock);
   264	
   265		if (!ret && !strlen(param_governor) && drv->governor &&
   266		    (cpuidle_get_driver() == drv)) {
   267			mutex_lock(&cpuidle_lock);
   268			gov = cpuidle_find_governor(drv->governor);
   269			if (gov) {
 > 270				cpuidle_prev_governor = cpuidle_curr_governor;
   271				if (cpuidle_switch_governor(gov) < 0)
   272					cpuidle_prev_governor = NULL;
   273			}
   274			mutex_unlock(&cpuidle_lock);
   275		}
   276	
   277		return ret;
   278	}
   279	EXPORT_SYMBOL_GPL(cpuidle_register_driver);
   280	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 48009 bytes --]

             reply	other threads:[~2019-09-06 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 16:44 kbuild test robot [this message]
2019-09-06 17:38 ` [pm:bleeding-edge 175/181] drivers/cpuidle/driver.c:270:4: error: 'cpuidle_prev_governor' undeclared; did you mean 'cpuidle_find_governor'? Joao Martins
2019-09-07 21:07   ` Rafael J. Wysocki

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=201909070020.yR8k4sTf%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=devel@acpica.org \
    --cc=joao.m.martins@oracle.com \
    --cc=kbuild-all@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).