From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Yifan Zhang <yifan1.zhang@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the amdgpu tree
Date: Tue, 27 Oct 2020 12:05:48 +1100 [thread overview]
Message-ID: <20201027120548.5618aa56@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
Hi all,
After merging the amdgpu tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c: In function 'amdgpu_dm_init':
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:947:34: warning: unused variable 'pa_config' [-Wunused-variable]
947 | struct dc_phy_addr_space_config pa_config;
| ^~~~~~~~~
At top level:
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:888:13: warning: 'mmhub_read_system_context' defined but not used [-Wunused-function]
888 | static void mmhub_read_system_context(struct amdgpu_device *adev, struct dc_phy_addr_space_config *pa_config)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
Introduced by commit
0b08c54bb7a3 ("drm/amd/display: Fix the display corruption issue on Navi10")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-10-27 1:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 1:05 Stephen Rothwell [this message]
2021-01-11 3:38 linux-next: build warnings after merge of the amdgpu tree Stephen Rothwell
2021-01-11 3:38 ` Stephen Rothwell
2021-02-24 2:28 Stephen Rothwell
2021-02-24 4:09 ` Zhuo, Qingqing
2021-02-26 1:29 ` Stephen Rothwell
2022-08-11 2:10 Stephen Rothwell
2022-08-30 23:00 ` Stephen Rothwell
2022-10-05 0:34 ` Stephen Rothwell
2022-11-18 6:55 Stephen Rothwell
2022-11-18 6:55 ` Stephen Rothwell
2023-07-11 23:15 ` Stephen Rothwell
2023-07-11 23:15 ` Stephen Rothwell
2023-07-12 2:26 ` Randy Dunlap
2023-07-12 2:26 ` Randy Dunlap
2023-07-12 2:51 ` Stephen Rothwell
2023-07-12 2:51 ` Stephen Rothwell
2023-03-16 1:18 Stephen Rothwell
2023-04-12 4:41 Stephen Rothwell
2023-07-11 23:08 Stephen Rothwell
2023-07-11 23:08 ` Stephen Rothwell
2024-01-30 2:49 Stephen Rothwell
2024-04-21 23:52 ` Stephen Rothwell
2024-04-26 6:55 Stephen Rothwell
2024-04-26 7:20 ` Khatri, Sunil
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=20201027120548.5618aa56@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexdeucher@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=yifan1.zhang@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.