From: kernel test robot <lkp@intel.com>
To: Eugen Hristev <eugen.hristev@linaro.org>, linux-arm-msm@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, andersson@kernel.org,
konradybcio@kernel.org, linux-kernel@vger.kernel.org,
Eugen Hristev <eugen.hristev@linaro.org>
Subject: Re: [PATCH] soc: qcom: Rework BCM_TCS_CMD macro
Date: Sat, 26 Oct 2024 05:06:51 +0800 [thread overview]
Message-ID: <202410260419.qGKBvJHZ-lkp@intel.com> (raw)
In-Reply-To: <20241025084823.475199-1-eugen.hristev@linaro.org>
Hi Eugen,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.12-rc4 next-20241025]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Eugen-Hristev/soc-qcom-Rework-BCM_TCS_CMD-macro/20241025-165212
base: linus/master
patch link: https://lore.kernel.org/r/20241025084823.475199-1-eugen.hristev%40linaro.org
patch subject: [PATCH] soc: qcom: Rework BCM_TCS_CMD macro
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20241026/202410260419.qGKBvJHZ-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241026/202410260419.qGKBvJHZ-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202410260419.qGKBvJHZ-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/soc/qcom/rpmh.h:9,
from drivers/clk/qcom/clk-rpmh.c:13:
drivers/clk/qcom/clk-rpmh.c: In function 'clk_rpmh_bcm_send_cmd':
>> include/soc/qcom/tcs.h:71:10: error: implicit declaration of function 'u32_encode_bits' [-Werror=implicit-function-declaration]
71 | (u32_encode_bits(commit, BCM_TCS_CMD_COMMIT_MASK) | \
| ^~~~~~~~~~~~~~~
drivers/clk/qcom/clk-rpmh.c:270:28: note: in expansion of macro 'BCM_TCS_CMD'
270 | cmd.data = BCM_TCS_CMD(1, enable, 0, cmd_state);
| ^~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/u32_encode_bits +71 include/soc/qcom/tcs.h
68
69 /* Construct a Bus Clock Manager (BCM) specific TCS command */
70 #define BCM_TCS_CMD(commit, valid, vote_x, vote_y) \
> 71 (u32_encode_bits(commit, BCM_TCS_CMD_COMMIT_MASK) | \
72 u32_encode_bits(valid, BCM_TCS_CMD_VALID_MASK) | \
73 u32_encode_bits((__force u32)cpu_to_le32(vote_x), \
74 BCM_TCS_CMD_VOTE_X_MASK) | \
75 u32_encode_bits((__force u32)cpu_to_le32(vote_y), \
76 BCM_TCS_CMD_VOTE_Y_MASK))
77
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-10-25 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 8:48 [PATCH] soc: qcom: Rework BCM_TCS_CMD macro Eugen Hristev
2024-10-25 9:03 ` Konrad Dybcio
2024-10-25 12:06 ` Eugen Hristev
2024-10-25 17:03 ` Konrad Dybcio
2024-10-28 12:22 ` Eugen Hristev
2024-10-25 21:06 ` kernel test robot [this message]
2024-10-26 7:47 ` kernel test robot
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=202410260419.qGKBvJHZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=eugen.hristev@linaro.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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