From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail•com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro•org>
Cc: Rob Clark <robdclark@gmail•com>,
Abhinav Kumar <quic_abhinavk@quicinc•com>,
Sean Paul <sean@poorly•run>, David Airlie <airlied@linux•ie>,
Daniel Vetter <daniel@ffwll•ch>,
linux-arm-msm@vger•kernel.org, dri-devel@lists•freedesktop.org,
freedreno@lists•freedesktop.org, linux-kernel@vger•kernel.org,
linux-next@vger•kernel.org, Nathan Chancellor <nathan@kernel•org>,
clang-built-linux <llvm@lists•linux.dev>
Subject: build failure of next-20220830 due to 5f8cdece42ff ("drm/msm/dsi: switch to DRM_PANEL_BRIDGE")
Date: Tue, 30 Aug 2022 10:18:43 +0100 [thread overview]
Message-ID: <Yw3V8yJgAnPD8o6P@debian> (raw)
Hi All,
The builds of arm64 allmodconfig with clang have failed to build
next-20220830 with the error:
drivers/gpu/drm/msm/dsi/dsi_host.c:1903:14: error: variable 'device_node' is uninitialized when used here [-Werror,-Wuninitialized]
of_node_put(device_node);
^~~~~~~~~~~
drivers/gpu/drm/msm/dsi/dsi_host.c:1870:44: note: initialize the variable 'device_node' to silence this warning
struct device_node *endpoint, *device_node;
^
= NULL
git bisect pointed to 5f8cdece42ff ("drm/msm/dsi: switch to DRM_PANEL_BRIDGE")
I will be happy to test any patch or provide any extra log if needed.
--
Regards
Sudip
next reply other threads:[~2022-08-30 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 9:18 Sudip Mukherjee (Codethink) [this message]
2022-08-30 12:40 ` build failure of next-20220830 due to 5f8cdece42ff ("drm/msm/dsi: switch to DRM_PANEL_BRIDGE") Nathan Chancellor
2022-08-30 20:43 ` Dmitry Baryshkov
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=Yw3V8yJgAnPD8o6P@debian \
--to=sudipm.mukherjee@gmail$(echo .)com \
--cc=airlied@linux$(echo .)ie \
--cc=daniel@ffwll$(echo .)ch \
--cc=dmitry.baryshkov@linaro$(echo .)org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=freedreno@lists$(echo .)freedesktop.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=nathan@kernel$(echo .)org \
--cc=quic_abhinavk@quicinc$(echo .)com \
--cc=robdclark@gmail$(echo .)com \
--cc=sean@poorly$(echo .)run \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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