From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Evan Quan <evan.quan@amd.com>
Cc: Alex Deucher <alexander.deucher@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 warning after merge of Linus' tree
Date: Thu, 20 Jan 2022 14:27:28 +1100 [thread overview]
Message-ID: <20220120142728.28b0ee58@canb.auug.org.au> (raw)
In-Reply-To: <20211123162938.2bfc30a7@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
Hi all,
On Tue, 23 Nov 2021 16:29:38 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Building Linus' tree, today's linux-next build (htmldocs) produced
> this warning:
>
> drivers/gpu/drm/amd/include/amd_shared.h:103: warning: Enum value 'AMD_IP_BLOCK_TYPE_NUM' not described in enum 'amd_ip_block_type'
>
> Introduced by commit
>
> 6ee27ee27ba8 ("drm/amd/pm: avoid duplicate powergate/ungate setting")
I am still seeing this warning.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-01-20 3:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 5:29 linux-next: build warning after merge of Linus' tree Stephen Rothwell
2022-01-20 3:27 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-27 2:10 Stephen Rothwell
2025-12-16 1:08 ` Stephen Rothwell
2025-04-22 10:47 Stephen Rothwell
2025-04-22 15:59 ` Linus Torvalds
2025-04-22 17:50 ` Thomas Weißschuh
2025-04-22 18:20 ` Linus Torvalds
2025-04-22 20:48 ` Nathan Chancellor
2025-04-22 20:49 ` Linus Torvalds
2025-04-27 11:42 ` David Laight
2025-04-22 23:55 ` Stephen Rothwell
2025-03-05 9:46 Stephen Rothwell
2024-10-01 3:47 Stephen Rothwell
2024-10-01 15:02 ` Christian Brauner
2024-03-13 4:04 Stephen Rothwell
2023-05-08 4:44 Stephen Rothwell
2023-05-08 6:28 ` Sakari Ailus
2021-10-05 9:18 Stephen Rothwell
2021-10-05 10:10 ` Jeff Layton
2021-10-01 7:18 Stephen Rothwell
2021-10-01 16:33 ` Eric Dumazet
2019-07-29 4:04 Stephen Rothwell
2019-07-29 6:58 ` Takashi Iwai
2019-07-29 7:03 ` Johannes Berg
2019-07-29 7:07 ` Takashi Iwai
2019-07-29 8:20 ` 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=20220120142728.28b0ee58@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexander.deucher@amd.com \
--cc=evan.quan@amd.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