From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alex Deucher <alexdeucher@gmail.com>, Dave Airlie <airlied@redhat.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Kun Liu <Kun.Liu2@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"DRI <dri-devel"@lists.freedesktop.org
Subject: Re: linux-next: build warning after merge of the amdgpu tree
Date: Thu, 16 Jan 2025 17:08:01 +1100 [thread overview]
Message-ID: <20250116170801.7ee67a21@canb.auug.org.au> (raw)
In-Reply-To: <20250113155423.3be0e78a@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
Hi all,
On Mon, 13 Jan 2025 15:54:23 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the amdgpu tree, today's linux-next build (htmldocs)
> produced this warning:
>
> drivers/gpu/drm/amd/include/amd_shared.h:352: warning: Enum value 'DC_DISABLE_HDMI_CEC' not described in enum 'DC_DEBUG_MASK'
>
> Introduced by commit
>
> 7594874227e1 ("drm/amd/display: add CEC notifier to amdgpu driver")
I am still seeing this warning. That commit is now in the drm tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2025-01-16 6:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250113155423.3be0e78a@canb.auug.org.au>
2025-01-16 6:08 ` Stephen Rothwell [this message]
[not found] <20240826155916.59ad7d57@canb.auug.org.au>
2024-09-06 8:46 ` linux-next: build warning after merge of the amdgpu tree Stephen Rothwell
[not found] <20240531152636.1b58caa0@canb.auug.org.au>
2024-07-14 23:07 ` Stephen Rothwell
[not found] <20240501151929.219916ee@canb.auug.org.au>
2024-07-14 23:02 ` Stephen Rothwell
2024-05-14 7:14 Stephen Rothwell
2024-05-14 18:20 ` Nirujogi, Pratap
2024-05-14 19:07 ` Alex Deucher
-- strict thread matches above, loose matches on Subject: below --
2024-05-14 7:11 Stephen Rothwell
2024-07-14 23:04 ` Stephen Rothwell
2024-01-30 2:56 Stephen Rothwell
2024-04-21 23:56 ` Stephen Rothwell
2024-07-14 22:59 ` Stephen Rothwell
2024-01-30 2:54 Stephen Rothwell
2024-04-21 23:54 ` Stephen Rothwell
2024-07-14 22:57 ` Stephen Rothwell
[not found] <20230815210747.6c409362@canb.auug.org.au>
2023-08-16 1:57 ` Stephen Rothwell
[not found] <20221026121428.5181969a@canb.auug.org.au>
2023-07-11 23:12 ` Stephen Rothwell
2023-06-09 4:02 Stephen Rothwell
2023-06-07 2:45 Stephen Rothwell
[not found] <20210416124044.53d4beee@canb.auug.org.au>
2021-04-21 6:40 ` Stephen Rothwell
2021-04-23 20:36 ` Alex Deucher
2021-04-23 22:39 ` Stephen Rothwell
[not found] <20210322170014.3e022928@canb.auug.org.au>
2021-04-21 6:15 ` Stephen Rothwell
[not found] <20210311220033.7c5fe548@canb.auug.org.au>
2021-04-21 6:10 ` Stephen Rothwell
[not found] <20210115120014.4211dec6@canb.auug.org.au>
[not found] ` <20210120171501.61aa0786@canb.auug.org.au>
2021-01-21 0:53 ` Stephen Rothwell
2021-01-21 3:07 ` Alex Deucher
2021-01-21 8:32 ` Daniel Vetter
[not found] <20201117154514.2c378d99@canb.auug.org.au>
2020-12-14 19:56 ` Stephen Rothwell
2020-12-15 2:49 ` Stephen Rothwell
2019-12-18 23:18 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=20250116170801.7ee67a21@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc="DRI <dri-devel"@lists.freedesktop.org \
--cc=Kun.Liu2@amd.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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