From: Nathan Chancellor <nathan@kernel.org>
To: Daniel Baluta <daniel.baluta@oss.nxp.com>
Cc: Daniel Baluta <daniel.baluta@nxp.com>,
andersson@kernel.org, konradybcio@kernel.org,
robin.clark@oss.qualcomm.com, dmitry.baryshkov@oss.qualcomm.com,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH v4 0/3] soc: qcom: ubwc: Fix link error
Date: Fri, 14 Aug 2026 10:06:21 -0700 [thread overview]
Message-ID: <20260814170621.GA532729@ax162> (raw)
In-Reply-To: <0b9128de-e2d9-4271-97b8-9fa0c7f6fa3c@oss.nxp.com>
On Fri, Aug 14, 2026 at 09:42:52AM +0300, Daniel Baluta wrote:
> On 8/14/26 02:23, Nathan Chancellor wrote:
> > In file included from drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp_v13.c:7:
> > include/linux/soc/qcom/ubwc.h: In function 'qcom_ubwc_config_get_data':
> > include/linux/soc/qcom/ubwc.h:45:16: error: implicit declaration of function 'ERR_PTR' [-Wimplicit-function-declaration]
> > 45 | return ERR_PTR(-EOPNOTSUPP);
> > | ^~~~~~~
> > include/linux/soc/qcom/ubwc.h:45:25: error: 'EOPNOTSUPP' undeclared (first use in this function)
>
> Hi Nathan,
>
> This issue is pre-existing and I've sent a separate fix for it:
>
> https://lore.kernel.org/all/5fy7l6o5nfzclsmhsqys562xwoilbo4xv3af65kcqugtitgltd@3fw2w443pw2g/#r
Sure, it is a pre-existing issue but it is only exposed by making
CONFIG_QCOM_UBWC_CONFIG an optional selection for these drivers, so I
think that patch should be a part of this series. Otherwise, I don't see
how you could actually trigger such an error.
--
Cheers,
Nathan
prev parent reply other threads:[~2026-08-14 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 15:19 [PATCH v4 0/3] soc: qcom: ubwc: Fix link error Daniel Baluta
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:50 ` sashiko-bot
2026-08-13 5:32 ` 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-12 15:32 ` sashiko-bot
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 [this message]
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=20260814170621.GA532729@ax162 \
--to=nathan@kernel.org \
--cc=andersson@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=daniel.baluta@oss.nxp.com \
--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=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