public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: ran jianping <ran.jianping@zte.com.cn>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: [andersson-remoteproc:ci-next 32/51] drivers/remoteproc/qcom_q6v5_adsp.c:178:56: error: expected ';' before 'if'
Date: Mon, 18 Jul 2022 01:14:37 +0800	[thread overview]
Message-ID: <202207180116.3mf56M5t-lkp@intel.com> (raw)

tree:   https://github.com/andersson/remoteproc ci-next
head:   7bd43ecf97f8237f4e2a7fdc27a26740b6afa92a
commit: dd0e63e9e8273d34512eed1d936640cba51f9c2a [32/51] remoteproc: qcom: using pm_runtime_resume_and_get to simplify the code
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20220718/202207180116.3mf56M5t-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/andersson/remoteproc/commit/dd0e63e9e8273d34512eed1d936640cba51f9c2a
        git remote add andersson-remoteproc https://github.com/andersson/remoteproc
        git fetch --no-tags andersson-remoteproc ci-next
        git checkout dd0e63e9e8273d34512eed1d936640cba51f9c2a
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/

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

All errors (new ones prefixed by >>):

   drivers/remoteproc/qcom_q6v5_adsp.c: In function 'qcom_rproc_pds_enable':
>> drivers/remoteproc/qcom_q6v5_adsp.c:178:56: error: expected ';' before 'if'
     178 |                 ret = pm_runtime_resume_and_get(pds[i])
         |                                                        ^
         |                                                        ;
     179 |                 if (ret < 0) {
         |                 ~~                                      
   drivers/remoteproc/qcom_q6v5_adsp.c:187:1: warning: label 'unroll_pd_votes' defined but not used [-Wunused-label]
     187 | unroll_pd_votes:
         | ^~~~~~~~~~~~~~~


vim +178 drivers/remoteproc/qcom_q6v5_adsp.c

   169	
   170	static int qcom_rproc_pds_enable(struct qcom_adsp *adsp, struct device **pds,
   171					 size_t pd_count)
   172	{
   173		int ret;
   174		int i;
   175	
   176		for (i = 0; i < pd_count; i++) {
   177			dev_pm_genpd_set_performance_state(pds[i], INT_MAX);
 > 178			ret = pm_runtime_resume_and_get(pds[i])
   179			if (ret < 0) {
   180				dev_pm_genpd_set_performance_state(pds[i], 0);
   181				goto unroll_pd_votes;
   182			}
   183		}
   184	
   185		return 0;
   186	
   187	unroll_pd_votes:
   188		for (i--; i >= 0; i--) {
   189			dev_pm_genpd_set_performance_state(pds[i], 0);
   190			pm_runtime_put(pds[i]);
   191		}
   192	
   193		return ret;
   194	}
   195	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-07-17 17:15 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=202207180116.3mf56M5t-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ran.jianping@zte.com.cn \
    /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