From: Nirmoy <nirmodas@amd•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Daniel Vetter <daniel.vetter@ffwll•ch>,
Intel Graphics <intel-gfx@lists•freedesktop.org>,
DRI <dri-devel@lists•freedesktop.org>
Cc: "Thomas Zimmermann" <tzimmermann@suse•de>,
"Christian König" <christian.koenig@amd•com>,
"Darren Salt" <devspam@moreofthesa•me.uk>,
"Nirmoy Das" <nirmoy.das@amd•com>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"Linux Next Mailing List" <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warnings after merge of the drm-misc tree
Date: Fri, 15 Jan 2021 16:03:59 +0100 [thread overview]
Message-ID: <9bb019ff-cbaa-3b1e-4688-80440a6d5c10@amd.com> (raw)
In-Reply-To: <20210115122310.7dd6bb11@canb.auug.org.au>
Hi Stephen,
On 1/15/21 2:23 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_display.c: In function 'amdgpu_display_user_framebuffer_create':
> drivers/gpu/drm/amd/amdgpu/amdgpu_display.c:929:24: warning: unused variable 'adev' [-Wunused-variable]
> 929 | struct amdgpu_device *adev = drm_to_adev(dev);
> | ^~~~
>
> Introduced by commit
>
> 8f66090b7bb7 ("drm/amdgpu: Remove references to struct drm_device.pdev")
I just sent a patch for this.
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c: In function 'amdgpu_device_resize_fb_bar':
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1109:6: warning: unused variable 'space_needed' [-Wunused-variable]
> 1109 | u64 space_needed = roundup_pow_of_two(adev->gmc.real_vram_size);
> | ^~~~~~~~~~~~
>
> Introduced by commit
>
> 453f617a30aa ("drm/amdgpu: Resize BAR0 to the maximum available size, even if it doesn't cover VRAM")
We have a fix already merged in drm-misc-next for this.
Thanks,
Nirmoy
>
next prev parent reply other threads:[~2021-01-15 15:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 1:23 linux-next: build warnings after merge of the drm-misc tree Stephen Rothwell
2021-01-15 15:03 ` Nirmoy [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-16 0:56 Stephen Rothwell
2025-11-10 2:50 Stephen Rothwell
2025-11-10 2:24 Stephen Rothwell
2025-11-05 5:18 Stephen Rothwell
2025-06-18 5:13 Stephen Rothwell
2025-06-11 4:09 Stephen Rothwell
2025-08-01 4:34 ` Stephen Rothwell
2025-08-01 11:04 ` Dmitry Baryshkov
2025-01-06 6:46 Stephen Rothwell
2025-01-14 5:43 ` Stephen Rothwell
2025-01-14 11:40 ` Dmitry Baryshkov
2025-01-14 12:06 ` Stephen Rothwell
2024-12-20 4:42 Stephen Rothwell
2025-01-14 5:41 ` Stephen Rothwell
2025-01-16 10:34 ` Tomi Valkeinen
2025-01-16 11:50 ` Maxime Ripard
2024-10-10 5:09 Stephen Rothwell
2024-10-10 8:35 ` Thomas Hellström
2024-10-10 5:04 Stephen Rothwell
2024-08-01 6:03 Stephen Rothwell
2024-04-16 7:31 Stephen Rothwell
2024-04-16 8:25 ` Jocelyn Falempe
2024-03-26 5:12 Stephen Rothwell
2023-12-04 4:53 Stephen Rothwell
2023-03-14 3:15 Stephen Rothwell
2022-06-11 8:21 Stephen Rothwell
2022-06-11 16:57 ` Doug Anderson
2022-04-06 5:44 Stephen Rothwell
2022-04-06 5:51 ` Stephen Rothwell
2022-04-13 0:07 ` Stephen Rothwell
2015-08-14 5:35 Stephen Rothwell
2015-08-14 12:51 ` Thierry Reding
2015-07-14 3:05 Stephen Rothwell
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=9bb019ff-cbaa-3b1e-4688-80440a6d5c10@amd.com \
--to=nirmodas@amd$(echo .)com \
--cc=christian.koenig@amd$(echo .)com \
--cc=daniel.vetter@ffwll$(echo .)ch \
--cc=devspam@moreofthesa$(echo .)me.uk \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nirmoy.das@amd$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tzimmermann@suse$(echo .)de \
/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