From: KernelCI bot <bot@kernelci.org>
To: kernelci-results@groups.io
Cc: soc@lists.linux.dev
Subject: [REGRESSION] soc/for-next: (build) ‘QCOM_ID_SDM850’ undeclared here (not in a function); did you mean...
Date: Tue, 04 Aug 2026 20:59:04 -0000 [thread overview]
Message-ID: <178587714419.6415.4839368342970024723@kernelci.org> (raw)
New build issue found on soc/for-next:
---
‘QCOM_ID_SDM850’ undeclared here (not in a function); did you mean ‘QCOM_ID_SDM450’? in drivers/soc/qcom/socinfo.o (drivers/soc/qcom/socinfo.c) [logspec:kbuild,kbuild.compiler.error]
---
Log excerpt:
=====================================================
drivers/soc/qcom/socinfo.c:25:27: error: ‘QCOM_ID_SDM850’ undeclared here (not in a function); did you mean ‘QCOM_ID_SDM450’?
25 | #define qcom_board_id(id) QCOM_ID_ ## id, __stringify(id)
| ^~~~~~~~
drivers/soc/qcom/socinfo.c:428:11: note: in expansion of macro ‘qcom_board_id’
428 | { qcom_board_id(SDM850) },
| ^~~~~~~~~~~~~
=====================================================
When fixing this issue, please attribute this report according to the
patch submission rules:
Reported-by: kernelci.org bot <bot@kernelci.org>
For complete logs and details about the environment used, see the issue
on the KernelCI dashboard:
- dashboard: https://d.kernelci.org/i/maestro:80d6d59b3a78228d8a8668e72eaa73c873b0edf2
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git
- commit HEAD: 81aa917982c10b9f2cd0dd767d7af5af6057d93d
# Builds where the incident occurred:
## defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y on (arm64):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-arm64-chromebook-6a724ed754179f15da9e53c2/.config
- dashboard: https://d.kernelci.org/build/maestro:6a724ed754179f15da9e53c2
## defconfig+netdev+nfs-root-boot+kselftest on (arm64):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-arm64-nfsboot-6a724ef454179f15da9e5466/.config
- dashboard: https://d.kernelci.org/build/maestro:6a724ef454179f15da9e5466
## multi_v7_defconfig on (arm):
- compiler: gcc-15
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a724ee454179f15da9e5456
#kernelci issue maestro:80d6d59b3a78228d8a8668e72eaa73c873b0edf2
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists.linux.dev
Made with love by the KernelCI team - https://kernelci.org
reply other threads:[~2026-08-04 20:59 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=178587714419.6415.4839368342970024723@kernelci.org \
--to=bot@kernelci.org \
--cc=kernelci-results@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=soc@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