From: Daniel Baluta <daniel.baluta@nxp.com>
To: andersson@kernel.org, konradybcio@kernel.org
Cc: robin.clark@oss.qualcomm.com, dmitry.baryshkov@oss.qualcomm.com,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
nathan@kernel.org, imx@lists.linux.dev,
Daniel Baluta <daniel.baluta@nxp.com>
Subject: [PATCH v4 0/3] soc: qcom: ubwc: Fix link error
Date: Wed, 12 Aug 2026 18:19:31 +0300 [thread overview]
Message-ID: <20260812151934.709198-1-daniel.baluta@nxp.com> (raw)
Fix link error caused by the fact that drivers/soc/qcom/ubwc_config.c
enabled via QCOM_UBWC_CONFIG uses unconditionally symbols from
drivers/soc/qcom/smem.c enabled via CONFIG_QCOM_SMEM.
Changes since v3:
- fix issues pointed by sashiko https://sashiko.dev/#/patchset/20260812130421.670527-1-daniel.baluta%40nxp.com
- add new patches 2/3 in order to fix unmet dependcy for VIDEO_QCOM_IRIS
- Use IS_REACHABLE instead of IS_ENABLED to avoid the situation we use
some symbols in builtin kernel but their definitions sits in a
module.
Remark for Dmitry, at this point I think v1 would have been a better
option.
Link to v1:
- https://lore.kernel.org/imx/1521da8e-18df-4d7b-a255-5ca133bd5ccc@oss.nxp.com/T/#t
Daniel Baluta (3):
soc: qcom: ubwc: Fix link error when QCOM_SMEM=n
media: iris: Fix unmet dependency when QCOM_SMEM=n
soc: qcom: ubwc: Use IS_REACHABLE() instead of IS_ENABLED()
drivers/gpu/drm/msm/Kconfig | 2 +-
drivers/media/platform/qcom/iris/Kconfig | 2 +-
drivers/soc/qcom/Kconfig | 1 +
include/linux/soc/qcom/ubwc.h | 2 +-
4 files changed, 4 insertions(+), 3 deletions(-)
--
2.45.2
next reply other threads:[~2026-08-12 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 15:19 Daniel Baluta [this message]
2026-08-12 15:19 ` [PATCH v4 1/3] soc: qcom: ubwc: Fix link error when QCOM_SMEM=n Daniel Baluta
2026-08-12 15:19 ` [PATCH v4 2/3] media: iris: Fix unmet dependency " Daniel Baluta
2026-08-12 15:19 ` [PATCH v4 3/3] soc: qcom: ubwc: Use IS_REACHABLE() instead of IS_ENABLED() Daniel Baluta
2026-08-13 23:23 ` [PATCH v4 0/3] soc: qcom: ubwc: Fix link error Nathan Chancellor
2026-08-14 6:42 ` Daniel Baluta
2026-08-14 17:06 ` Nathan Chancellor
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=20260812151934.709198-1-daniel.baluta@nxp.com \
--to=daniel.baluta@nxp.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=imx@lists.linux.dev \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=robin.clark@oss.qualcomm.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 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®