[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190531112752.7f3ca857@canb.auug.org.au>
Date: Fri, 31 May 2019 11:27:52 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Dave Airlie <airlied@...ux.ie>
Cc: Alex Deucher <alexdeucher@...il.com>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jonathan Kim <jonathan.kim@....com>
Subject: Re: linux-next: build warning after merge of the amdgpu tree
Hi all,
On Fri, 10 May 2019 10:59:13 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> After merging the amdgpu tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from drivers/gpu/drm/amd/amdgpu/df_v3_6.c:23:
> drivers/gpu/drm/amd/amdgpu/df_v3_6.c: In function 'df_v3_6_pmc_start':
> drivers/gpu/drm/amd/amdgpu/amdgpu.h:1010:29: warning: 'lo_val' may be used uninitialized in this function [-Wmaybe-uninitialized]
> #define WREG32_PCIE(reg, v) adev->pcie_wreg(adev, (reg), (v))
> ^~~~
> drivers/gpu/drm/amd/amdgpu/df_v3_6.c:334:39: note: 'lo_val' was declared here
> uint32_t lo_base_addr, hi_base_addr, lo_val, hi_val;
> ^~~~~~
>
> Introduced by commit
>
> a6ac0b44bab9 ("drm/amdgpu: add df perfmon regs and funcs for xgmi")
I now get this warning after merging the drm tree ...
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists