From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alex Deucher <alexdeucher@gmail•com>
Cc: "Zhuo, Qingqing" <Qingqing.Zhuo@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 amdgpu tree
Date: Fri, 26 Feb 2021 12:29:59 +1100 [thread overview]
Message-ID: <20210226122959.68baae71@canb.auug.org.au> (raw)
In-Reply-To: <DM6PR12MB29394B1C0B88CE17F8CB98D4FB9F9@DM6PR12MB2939.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
Hi all,
On Wed, 24 Feb 2021 04:09:31 +0000 "Zhuo, Qingqing" <Qingqing.Zhuo@amd•com> wrote:
>
> [AMD Public Use]
>
> Hi Stephen,
>
> Thanks for your feedback. I will submit a fix for the warning.
>
> Thank you,
> Lillian
>
> -----Original Message-----
> From: Stephen Rothwell <sfr@canb•auug.org.au>
> Sent: Tuesday, February 23, 2021 9:29 PM
> To: Alex Deucher <alexdeucher@gmail•com>
> Cc: Zhuo, Qingqing <Qingqing.Zhuo@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
>
> Hi all,
>
> After merging the amdgpu tree, today's linux-next build (htmldocs) produced these warnings:
>
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:380: warning: Function parameter or member 'vblank_lock' not described in 'amdgpu_display_manager'
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:380: warning: Function parameter or member 'vblank_workqueue' not described in 'amdgpu_display_manager'
>
> Introduced by commit
>
> 3cfd14b67b2c ("drm/amd/display: Fix system hang after multiple hotplugs (v2)")
Those warnings have now made it into Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-02-26 1:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 2:28 linux-next: build warnings after merge of the amdgpu tree Stephen Rothwell
2021-02-24 4:09 ` Zhuo, Qingqing
2021-02-26 1:29 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-20 3:39 Stephen Rothwell
2024-04-26 6:55 Stephen Rothwell
2024-04-26 7:20 ` Khatri, Sunil
2024-01-30 2:49 Stephen Rothwell
2024-04-21 23:52 ` Stephen Rothwell
2023-07-11 23:08 Stephen Rothwell
2023-04-12 4:41 Stephen Rothwell
2023-03-16 1:18 Stephen Rothwell
2022-11-18 6:55 Stephen Rothwell
2023-07-11 23:15 ` Stephen Rothwell
2023-07-12 2:26 ` Randy Dunlap
2023-07-12 2:51 ` Stephen Rothwell
2022-08-11 2:10 Stephen Rothwell
2022-08-30 23:00 ` Stephen Rothwell
2022-10-05 0:34 ` Stephen Rothwell
2021-01-11 3:38 Stephen Rothwell
2020-10-27 1: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=20210226122959.68baae71@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Qingqing.Zhuo@amd$(echo .)com \
--cc=alexdeucher@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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