From: kernel test robot <lkp@intel.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
kbuild-all@lists.01.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [clk:clk-qcom 27/42] drivers/clk/qcom/gpucc-msm8998.c:265:45: error: 'NO_RET_PERIPH' undeclared here (not in a function)
Date: Sun, 14 Feb 2021 20:52:28 +0800 [thread overview]
Message-ID: <202102142027.QnL2H9Am-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2133 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-qcom
head: 27aef2b9462a57798e9bc54bf471ed39cf60117a
commit: 1e40c64b4026021a11bba22253741bb40141b778 [27/42] clk: qcom: gpucc-msm8998: Add resets, cxc, fix flags on gpu_gx_gdsc
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.3.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://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/commit/?id=1e40c64b4026021a11bba22253741bb40141b778
git remote add clk https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
git fetch --no-tags clk clk-qcom
git checkout 1e40c64b4026021a11bba22253741bb40141b778
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the clk/clk-qcom HEAD 27aef2b9462a57798e9bc54bf471ed39cf60117a builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
>> drivers/clk/qcom/gpucc-msm8998.c:265:45: error: 'NO_RET_PERIPH' undeclared here (not in a function)
265 | .flags = CLAMP_IO | SW_RESET | AON_RESET | NO_RET_PERIPH,
| ^~~~~~~~~~~~~
vim +/NO_RET_PERIPH +265 drivers/clk/qcom/gpucc-msm8998.c
252
253 static struct gdsc gpu_gx_gdsc = {
254 .gdscr = 0x1094,
255 .clamp_io_ctrl = 0x130,
256 .resets = (unsigned int []){ GPU_GX_BCR },
257 .reset_count = 1,
258 .cxcs = (unsigned int []){ 0x1098 },
259 .cxc_count = 1,
260 .pd = {
261 .name = "gpu_gx",
262 },
263 .parent = &gpu_cx_gdsc.pd,
264 .pwrsts = PWRSTS_OFF_ON | PWRSTS_RET,
> 265 .flags = CLAMP_IO | SW_RESET | AON_RESET | NO_RET_PERIPH,
266 };
267
---
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: 72497 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-02-14 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 12:52 kernel test robot [this message]
2021-02-14 20:57 ` [clk:clk-qcom 27/42] drivers/clk/qcom/gpucc-msm8998.c:265:45: error: 'NO_RET_PERIPH' undeclared here (not in a function) Stephen Boyd
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=202102142027.QnL2H9Am-lkp@intel.com \
--to=lkp@intel.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).