From: kernel test robot <lkp@intel.com>
To: Kuogee Hsieh <quic_khsieh@quicinc.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Vinod Koul <vkoul@kernel.org>, Kishon <kishon@ti.com>,
linux-kernel@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>,
Douglas Anderson <dianders@chromium.org>
Subject: [phy:next 74/75] drivers/phy/qualcomm/phy-qcom-qmp-combo.c:2004:2: error: use of undeclared identifier 'Return'
Date: Thu, 7 Jul 2022 06:36:52 +0800 [thread overview]
Message-ID: <202207070605.0xk0pmxE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git next
head: fa384dd8b9b8dd3621b8f91c849386a4295d1b01
commit: 6bd9a9be5d732e7697804cba075f11a12dfa6bd3 [74/75] phy: qcom-qmp: add regulator_set_load to dp phy
config: riscv-buildonly-randconfig-r006-20220706 (https://download.01.org/0day-ci/archive/20220707/202207070605.0xk0pmxE-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project f553287b588916de09c66e3e32bf75e5060f967f)
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
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git/commit/?id=6bd9a9be5d732e7697804cba075f11a12dfa6bd3
git remote add phy https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git
git fetch --no-tags phy next
git checkout 6bd9a9be5d732e7697804cba075f11a12dfa6bd3
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash drivers/phy/qualcomm/
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/phy/qualcomm/phy-qcom-qmp-combo.c:2004:2: error: use of undeclared identifier 'Return'
Return 0;
^
1 error generated.
vim +/Return +2004 drivers/phy/qualcomm/phy-qcom-qmp-combo.c
1974
1975 static int qcom_qmp_phy_combo_vreg_init(struct device *dev, const struct qmp_phy_cfg *cfg)
1976 {
1977 struct qcom_qmp *qmp = dev_get_drvdata(dev);
1978 int num = cfg->num_vregs;
1979 int ret, i;
1980
1981 qmp->vregs = devm_kcalloc(dev, num, sizeof(*qmp->vregs), GFP_KERNEL);
1982 if (!qmp->vregs)
1983 return -ENOMEM;
1984
1985 for (i = 0; i < num; i++)
1986 qmp->vregs[i].supply = cfg->vreg_list[i].name;
1987
1988 ret = devm_regulator_bulk_get(dev, num, qmp->vregs);
1989 if (ret) {
1990 dev_err(dev, "failed at devm_regulator_bulk_get\n");
1991 return ret;
1992 }
1993
1994 for (i = 0; i < num; i++) {
1995 ret = regulator_set_load(qmp->vregs[i].consumer,
1996 cfg->vreg_list[i].enable_load);
1997 if (ret) {
1998 dev_err(dev, "failed to set load at %s\n",
1999 qmp->vregs[i].supply);
2000 return ret;
2001 }
2002 }
2003
> 2004 Return 0;
2005 }
2006
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-06 22:37 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=202207070605.0xk0pmxE-lkp@intel.com \
--to=lkp@intel.com \
--cc=dianders@chromium.org \
--cc=kbuild-all@lists.01.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=quic_khsieh@quicinc.com \
--cc=swboyd@chromium.org \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®