From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andy Gross <agross@codeaurora.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Boyd <swboyd@chromium.org>
Subject: Re: linux-next: build warning after merge of the qcom tree
Date: Thu, 29 Nov 2018 08:25:40 +1100 [thread overview]
Message-ID: <20181129082540.4ceafca6@canb.auug.org.au> (raw)
In-Reply-To: <20181116101059.18ad3fc9@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
Hi all,
On Fri, 16 Nov 2018 10:10:59 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the qcom tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/gpu/drm/msm/adreno/a6xx_gmu.c: In function 'a6xx_gmu_rpmh_arc_votes_init.constprop':
> drivers/gpu/drm/msm/adreno/a6xx_gmu.c:943:12: warning: 'pri_count' is used uninitialized in this function [-Wuninitialized]
> pri_count >>= 1;
> ^~~
> drivers/gpu/drm/msm/adreno/a6xx_gmu.c:948:12: warning: 'sec_count' may be used uninitialized in this function [-Wmaybe-uninitialized]
> sec_count >>= 1;
> ^~~
>
> Introduced by commit
>
> ed3cafa79ea7 ("soc: qcom: cmd-db: Stop memcpy()ing in cmd_db_read_aux_data()")
>
> # CONFIG_QCOM_COMMAND_DB is not set
I am still getting these warnings.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-28 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 23:10 linux-next: build warning after merge of the qcom tree Stephen Rothwell
2018-11-28 21:25 ` Stephen Rothwell [this message]
2018-11-29 16:30 ` Stephen Boyd
2018-11-30 4:13 ` Stephen Rothwell
2019-08-07 0:08 Stephen Rothwell
2020-04-15 0:25 Stephen Rothwell
2020-04-15 4:51 ` Stephen Boyd
2020-04-15 5:04 ` Bjorn Andersson
2021-10-24 23:28 Stephen Rothwell
2021-10-24 23:40 ` David Heidelberg
2021-10-25 2:24 ` Bjorn Andersson
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=20181129082540.4ceafca6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agross@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=swboyd@chromium.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).