From: Simon Horman <simon.horman@corigine.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, llvm@lists.linux.dev,
linux-phy@lists.infradead.org,
"moderated list:ARM/Mediatek SoC..."
<linux-mediatek@lists.infradead.org>,
Guillaume Ranquet <granquet@baylibre.com>,
Vinod Koul <vkoul@kernel.org>, Kishon <kishon@ti.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Netdev <netdev@vger.kernel.org>,
chunfeng.yun@mediatek.com
Subject: Re: next: allmodconfig: phy-mtk-hdmi-mt8195.c:298:6: error: variable 'ret' is uninitialized when used here [-Werror,-Wuninitialized]
Date: Tue, 18 Apr 2023 16:17:10 +0200 [thread overview]
Message-ID: <ZD6mZv2n2yUZKA1G@corigine.com> (raw)
In-Reply-To: <CA+G9fYu4o0-ZKSthi7kdCjz_kFazZS-rn17Z2NPz3=1Oayr9cw@mail.gmail.com>
On Fri, Apr 14, 2023 at 03:14:27PM +0530, Naresh Kamboju wrote:
> Following build warnings / errors noticed while building allmodconfig for arm64
> with clang-16 on Linux next-20230414.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> drivers/phy/mediatek/phy-mtk-hdmi-mt8195.c:298:6: error: variable
> 'ret' is uninitialized when used here [-Werror,-Wuninitialized]
> if (ret)
> ^~~
> drivers/phy/mediatek/phy-mtk-hdmi-mt8195.c:216:12: note: initialize
> the variable 'ret' to silence this warning
> int i, ret;
> ^
> = 0
> 1 error generated.
I believe a fix for this has been submitted but not yet applied.
- [PATCH v2 1/2] phy: mediatek: hdmi: mt8195: fix uninitialized variable usage in pll_calc
Link: https://lore.kernel.org/all/20230413-fixes-for-mt8195-hdmi-phy-v2-1-bbad62e64321@baylibre.com/
prev parent reply other threads:[~2023-04-18 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 9:44 next: allmodconfig: phy-mtk-hdmi-mt8195.c:298:6: error: variable 'ret' is uninitialized when used here [-Werror,-Wuninitialized] Naresh Kamboju
2023-04-18 14:17 ` Simon Horman [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=ZD6mZv2n2yUZKA1G@corigine.com \
--to=simon.horman@corigine.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunfeng.yun@mediatek.com \
--cc=granquet@baylibre.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=vkoul@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).