From: kernel test robot <lkp@intel.com>
To: Sreeshankar K <sreeshankar0910@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Abel Vesa <abel.vesa@oss.qualcomm.com>
Subject: [linux-next:master 1663/8910] drivers/soc/qcom/socinfo.c:25:27: error: 'QCOM_ID_SM7250' undeclared here (not in a function); did you mean 'QCOM_ID_SM7750'?
Date: Thu, 24 Sep 2026 07:16:43 +0800 [thread overview]
Message-ID: <202609240715.gpsuNHCe-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: a8c591ed6b672915e0be57843f943a2a723aff40
commit: aa186658b79e993365b4b2153813474d8b928da1 [1663/8910] soc: qcom: socinfo: Add SM7250 SoC ID
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20260924/202609240715.gpsuNHCe-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260924/202609240715.gpsuNHCe-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/202609240715.gpsuNHCe-lkp@intel.com/
Note: the linux-next/master HEAD a8c591ed6b672915e0be57843f943a2a723aff40 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
>> drivers/soc/qcom/socinfo.c:25:27: error: 'QCOM_ID_SM7250' undeclared here (not in a function); did you mean 'QCOM_ID_SM7750'?
25 | #define qcom_board_id(id) QCOM_ID_ ## id, __stringify(id)
| ^~~~~~~~
drivers/soc/qcom/socinfo.c:453:11: note: in expansion of macro 'qcom_board_id'
453 | { qcom_board_id(SM7250) },
| ^~~~~~~~~~~~~
vim +25 drivers/soc/qcom/socinfo.c
34ec89e68db268 Krzysztof Kozlowski 2022-08-30 23
34ec89e68db268 Krzysztof Kozlowski 2022-08-30 24 /* Helper macros to create soc_id table */
34ec89e68db268 Krzysztof Kozlowski 2022-08-30 @25 #define qcom_board_id(id) QCOM_ID_ ## id, __stringify(id)
34ec89e68db268 Krzysztof Kozlowski 2022-08-30 26 #define qcom_board_id_named(id, name) QCOM_ID_ ## id, (name)
34ec89e68db268 Krzysztof Kozlowski 2022-08-30 27
:::::: The code at line 25 was first introduced by commit
:::::: 34ec89e68db2682469a9a51d9ed4022ee3992389 soc: qcom: socinfo: create soc_id table from bindings
:::::: TO: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
:::::: CC: Bjorn Andersson <andersson@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-23 23:16 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=202609240715.gpsuNHCe-lkp@intel.com \
--to=lkp@intel.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=lumag@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sreeshankar0910@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.