Linux Power Management development
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: kbuild-all@01.org, linux-acpi@vger.kernel.org, devel@acpica.org,
	linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Matthias Kaehlcke <mka@chromium.org>,
	Ulf Hansson <ulf.hansson@linaro.org>
Subject: [pm:linux-next 91/102] include/linux/pm_qos.h:197:9: error: expected '(' before 'type'
Date: Thu, 4 Jul 2019 09:04:00 +0800	[thread overview]
Message-ID: <201907040956.ywZASIcA%lkp@intel.com> (raw)

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

tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
head:   267eacd79cadd5e2d6307320497d66119907c411
commit: 57fa6137402b98327d1247c5aaf3d4f0595a73fe [91/102] PM / QOS: Pass request type to dev_pm_qos_read_value()
config: riscv-allnoconfig (attached as .config)
compiler: riscv64-linux-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 57fa6137402b98327d1247c5aaf3d4f0595a73fe
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=riscv 

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

All error/warnings (new ones prefixed by >>):

   In file included from kernel//power/qos.c:33:0:
   include/linux/pm_qos.h: In function 'dev_pm_qos_read_value':
>> include/linux/pm_qos.h:197:9: error: expected '(' before 'type'
     switch type {
            ^~~~
   include/linux/pm_qos.h:197:9: warning: statement with no effect [-Wunused-value]
>> include/linux/pm_qos.h:204:1: warning: no return statement in function returning non-void [-Wreturn-type]
    }
    ^
   include/linux/pm_qos.h: At top level:
   include/linux/pm_qos.h:219:4: error: expected identifier or '(' before '{' token
       { return 0; }
       ^
   include/linux/pm_qos.h:216:19: warning: 'dev_pm_qos_add_notifier' declared 'static' but never defined [-Wunused-function]
    static inline int dev_pm_qos_add_notifier(struct device *dev,
                      ^~~~~~~~~~~~~~~~~~~~~~~

vim +197 include/linux/pm_qos.h

   178	
   179	static inline s32 dev_pm_qos_raw_resume_latency(struct device *dev)
   180	{
   181		return IS_ERR_OR_NULL(dev->power.qos) ?
   182			PM_QOS_RESUME_LATENCY_NO_CONSTRAINT :
   183			pm_qos_read_value(&dev->power.qos->resume_latency);
   184	}
   185	#else
   186	static inline enum pm_qos_flags_status __dev_pm_qos_flags(struct device *dev,
   187								  s32 mask)
   188				{ return PM_QOS_FLAGS_UNDEFINED; }
   189	static inline enum pm_qos_flags_status dev_pm_qos_flags(struct device *dev,
   190								s32 mask)
   191				{ return PM_QOS_FLAGS_UNDEFINED; }
   192	static inline s32 __dev_pm_qos_resume_latency(struct device *dev)
   193				{ return PM_QOS_RESUME_LATENCY_NO_CONSTRAINT; }
   194	static inline s32 dev_pm_qos_read_value(struct device *dev,
   195						enum dev_pm_qos_req_type type)
   196	{
 > 197		switch type {
   198		case DEV_PM_QOS_RESUME_LATENCY:
   199			return PM_QOS_RESUME_LATENCY_NO_CONSTRAINT;
   200		default:
   201			WARN_ON(1);
   202			return 0;
   203		}
 > 204	}
   205	

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

             reply	other threads:[~2019-07-04  1:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04  1:04 kbuild test robot [this message]
2019-07-04  3:18 ` [pm:linux-next 91/102] include/linux/pm_qos.h:197:9: error: expected '(' before 'type' Viresh Kumar

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=201907040956.ywZASIcA%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=devel@acpica.org \
    --cc=kbuild-all@01.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=rjw@rjwysocki.net \
    --cc=ulf.hansson@linaro.org \
    --cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox