From: Alex Hung <alex.hung@amd.com>
To: "Zhu, Yihan" <Yihan.Zhu@amd.com>, Alex Deucher <alexdeucher@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"LIPSKI, IVAN" <IVAN.LIPSKI@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Kazlauskas, Nicholas" <Nicholas.Kazlauskas@amd.com>
Subject: Re: linux-next: build warning after merge of the amdgpu tree
Date: Wed, 16 Jul 2025 13:40:38 -0600 [thread overview]
Message-ID: <f6f7bd35-cea6-477f-84d3-f3ce6bf5bd85@amd.com> (raw)
In-Reply-To: <IA1PR12MB60448C621D9999334E7DF264E356A@IA1PR12MB6044.namprd12.prod.outlook.com>
On 7/16/25 13:24, Zhu, Yihan wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hi Alex,
>
> I just double checked this parameter might be missing from upstream. I will work with Alex Hung or can you pls help me to add descriptions below to patch? Thanks
>
> * @num_rmcm_3dluts: number of RMCM hardware instance
I will create and send a patch shortly.
>
> Regards,
> Yihan Z
>
> -----Original Message-----
> From: Alex Deucher <alexdeucher@gmail.com>
> Sent: Wednesday, July 16, 2025 3:09 PM
> To: Zhu, Yihan <Yihan.Zhu@amd.com>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>; Hung, Alex <Alex.Hung@amd.com>; Deucher, Alexander <Alexander.Deucher@amd.com>; LIPSKI, IVAN <IVAN.LIPSKI@amd.com>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Linux Next Mailing List <linux-next@vger.kernel.org>; Kazlauskas, Nicholas <Nicholas.Kazlauskas@amd.com>
> Subject: Re: linux-next: build warning after merge of the amdgpu tree
>
> On Wed, Jul 16, 2025 at 2:45 PM Zhu, Yihan <Yihan.Zhu@amd.com> wrote:
>>
>> [AMD Official Use Only - AMD Internal Distribution Only]
>>
>> Hi,
>>
>> +Alex Hung +Nick for awareness.
>>
>> Thanks for the information. I believe Alex helped me to add the description in another patch. Please let me know if any further actions from me.
>
> Has the fix been sent out yet? I don't remember seeing it.
>
> Alex
>
>
>>
>> Regards,
>> Yihan Z
>>
>> -----Original Message-----
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Sent: Wednesday, July 16, 2025 6:29 AM
>> To: Alex Deucher <alexdeucher@gmail.com>
>> Cc: Deucher, Alexander <Alexander.Deucher@amd.com>; LIPSKI, IVAN <IVAN.LIPSKI@amd.com>; Zhu, Yihan <Yihan.Zhu@amd.com>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Linux Next Mailing List <linux-next@vger.kernel.org>
>> Subject: linux-next: build warning after merge of the amdgpu tree
>>
>> Hi all,
>>
>> After merging the amdgpu tree, today's linux-next build (htmldocs) produced this warning:
>>
>> drivers/gpu/drm/amd/display/dc/dc.h:255: warning: Function parameter or struct member 'num_rmcm_3dluts' not described in 'mpc_color_caps'
>>
>> Introduced by commit
>>
>> 26ad78fffc66 ("drm/amd/display: MPC basic allocation logic and TMZ")
>>
>> --
>> Cheers,
>> Stephen Rothwell
next prev parent reply other threads:[~2025-07-16 19:40 UTC|newest]
Thread overview: 147+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 10:28 linux-next: build warning after merge of the amdgpu tree Stephen Rothwell
2025-07-16 18:45 ` Zhu, Yihan
2025-07-16 19:08 ` Alex Deucher
2025-07-16 19:24 ` Zhu, Yihan
2025-07-16 19:40 ` Alex Hung [this message]
2025-07-17 2:15 ` Randy Dunlap
2025-08-01 4:45 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-11-19 2:22 Stephen Rothwell
2025-12-16 1:07 ` Stephen Rothwell
2025-08-05 3:11 Stephen Rothwell
2025-08-05 14:11 ` Aurabindo Pillai
2025-06-19 10:59 Stephen Rothwell
2025-06-04 3:23 Stephen Rothwell
2025-06-04 13:31 ` Zhu, Yihan
2025-05-09 8:58 Stephen Rothwell
2025-04-22 10:33 Stephen Rothwell
2025-06-03 22:57 ` Stephen Rothwell
2025-04-22 10:29 Stephen Rothwell
2025-04-09 3:10 Stephen Rothwell
2025-04-10 4:40 ` Stephen Rothwell
2025-04-10 19:11 ` Li, Roman
2025-03-19 9:34 Stephen Rothwell
2025-03-19 9:38 ` Kaszewski, Dominik
2025-03-19 11:00 ` Stephen Rothwell
2025-03-19 11:13 ` Kaszewski, Dominik
2025-04-03 6:01 ` Stephen Rothwell
2025-04-03 6:08 ` Kaszewski, Dominik
2025-02-26 4:44 Stephen Rothwell
2025-01-17 5:45 Stephen Rothwell
2025-01-13 4:54 Stephen Rothwell
2025-01-16 6:08 ` Stephen Rothwell
2024-10-02 4:17 Stephen Rothwell
2024-08-26 5:59 Stephen Rothwell
2024-09-06 8:46 ` Stephen Rothwell
2024-05-31 5:26 Stephen Rothwell
2024-07-14 23:07 ` Stephen Rothwell
2024-05-14 7:14 Stephen Rothwell
2024-05-14 18:20 ` Nirujogi, Pratap
2024-05-14 19:07 ` Alex Deucher
2024-05-14 7:11 Stephen Rothwell
2024-07-14 23:04 ` Stephen Rothwell
2024-05-01 5:19 Stephen Rothwell
2024-07-14 23:02 ` Stephen Rothwell
2024-01-30 2:56 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-01-30 2:54 ` Stephen Rothwell
2024-04-21 23:54 ` Stephen Rothwell
2024-07-14 22:57 ` Stephen Rothwell
2023-12-14 4:29 Stephen Rothwell
2023-12-12 0:04 Stephen Rothwell
2023-12-12 3:01 ` Stephen Rothwell
2023-12-12 9:01 ` Melissa Wen
2023-12-12 15:05 ` Alex Deucher
2023-10-17 3:35 Stephen Rothwell
2023-09-21 2:31 Stephen Rothwell
2023-08-15 11:07 Stephen Rothwell
2023-08-16 1:57 ` Stephen Rothwell
2023-08-16 1:57 ` Stephen Rothwell
2023-08-16 20:45 ` Alex Deucher
2023-06-09 4:02 Stephen Rothwell
2023-06-09 4:02 ` Stephen Rothwell
2023-06-07 2:45 Stephen Rothwell
2023-06-07 2:45 ` Stephen Rothwell
2023-04-12 4:36 Stephen Rothwell
2023-04-03 7:42 Stephen Rothwell
2023-03-01 0:34 Stephen Rothwell
2023-02-15 4:13 Stephen Rothwell
2023-01-18 3:13 Stephen Rothwell
2022-12-15 0:35 Stephen Rothwell
2022-11-18 6:47 Stephen Rothwell
2022-11-18 8:29 ` Christian König
2022-11-10 7:23 Stephen Rothwell
2022-10-28 3:33 Stephen Rothwell
2022-10-26 1:14 Stephen Rothwell
2023-07-11 23:12 ` Stephen Rothwell
2023-07-11 23:12 ` Stephen Rothwell
2022-10-24 4:14 Stephen Rothwell
2022-08-31 5:37 Stephen Rothwell
2022-10-09 22:58 ` Stephen Rothwell
2022-08-11 22:13 Stephen Rothwell
2022-08-30 23:04 ` Stephen Rothwell
2022-10-05 0:36 ` Stephen Rothwell
2022-08-11 2:05 Stephen Rothwell
2022-08-30 1:48 ` Stephen Rothwell
2022-06-23 7:47 Stephen Rothwell
2022-03-25 8:07 Stephen Rothwell
2022-03-25 8:11 ` Christian König
2021-08-25 2:51 Stephen Rothwell
2021-06-05 2:26 Stephen Rothwell
2021-06-05 14:39 ` Eric Huang
2021-06-03 9:22 Stephen Rothwell
2021-05-28 1:50 Stephen Rothwell
2021-05-04 23:39 Stephen Rothwell
[not found] ` <DM4PR12MB5133E6A99840D1E8542C0D23F7599@DM4PR12MB5133.namprd12.prod.outlook.com>
2021-05-05 2:55 ` Stephen Rothwell
2021-04-26 12:40 Stephen Rothwell
2021-04-26 14:40 ` Nirmoy
2021-04-16 2:40 Stephen Rothwell
2021-04-16 3:12 ` Liang, Prike
2021-04-16 4:08 ` Stephen Rothwell
2021-04-16 5:47 ` Liang, Prike
2021-04-16 5:51 ` Alex Deucher
2021-04-21 6:40 ` Stephen Rothwell
2021-04-21 6:40 ` Stephen Rothwell
2021-04-23 20:36 ` Alex Deucher
2021-04-23 20:36 ` Alex Deucher
2021-04-23 22:39 ` Stephen Rothwell
2021-04-23 22:39 ` Stephen Rothwell
2021-03-24 6:48 Stephen Rothwell
2021-03-24 2:33 Stephen Rothwell
2021-03-22 6:00 Stephen Rothwell
2021-04-21 6:15 ` Stephen Rothwell
2021-04-21 6:15 ` Stephen Rothwell
2021-03-11 11:00 Stephen Rothwell
2021-04-21 6:10 ` Stephen Rothwell
2021-04-21 6:10 ` Stephen Rothwell
2021-03-09 2:55 Stephen Rothwell
2021-03-03 6:00 Stephen Rothwell
2021-02-23 23:48 Stephen Rothwell
2021-01-18 5:29 Stephen Rothwell
2021-01-18 5:56 ` Huang, Ray
2021-01-18 6:52 ` Stephen Rothwell
2021-01-18 12:35 ` Huang Rui
2021-01-15 1:00 Stephen Rothwell
2021-01-20 6:15 ` Stephen Rothwell
2021-01-21 0:53 ` Stephen Rothwell
2021-01-21 0:53 ` Stephen Rothwell
2021-01-21 3:07 ` Alex Deucher
2021-01-21 3:07 ` Alex Deucher
2021-01-21 8:32 ` Daniel Vetter
2021-01-21 8:32 ` Daniel Vetter
2020-11-17 4:45 Stephen Rothwell
2020-12-14 19:56 ` Stephen Rothwell
2020-12-14 19:56 ` Stephen Rothwell
2020-12-15 2:49 ` Stephen Rothwell
2020-12-15 2:49 ` Stephen Rothwell
2020-04-23 2:24 Stephen Rothwell
2020-03-13 9:57 Stephen Rothwell
2020-02-04 22:44 Stephen Rothwell
2019-12-18 23:18 Stephen Rothwell
2019-12-18 23:18 ` Stephen Rothwell
2019-11-08 0:21 Stephen Rothwell
2019-07-02 3:53 Stephen Rothwell
2019-05-10 0:59 Stephen Rothwell
2019-05-31 1:27 ` 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=f6f7bd35-cea6-477f-84d3-f3ce6bf5bd85@amd.com \
--to=alex.hung@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=IVAN.LIPSKI@amd.com \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=Yihan.Zhu@amd.com \
--cc=alexdeucher@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.