From: Hamza Mahfooz <hamza.mahfooz@amd.com>
To: "Ho, Kenny" <Kenny.Ho@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Kuehling, Felix" <Felix.Kuehling@amd.com>,
"Wentland, Harry" <Harry.Wentland@amd.com>,
"André Almeida" <andrealmeid@igalia.com>,
"Andrew Davis" <afd@ti.com>, "Peter Foley" <pefoley2@pefoley.com>,
"Zhang, Hawking" <Hawking.Zhang@amd.com>,
"Ma, Le" <Le.Ma@amd.com>, "Zhou1, Tao" <Tao.Zhou1@amd.com>,
"Lazar, Lijo" <Lijo.Lazar@amd.com>,
"Zhu, James" <James.Zhu@amd.com>,
"Chai, Thomas" <YiPeng.Chai@amd.com>,
"Li, Candice" <Candice.Li@amd.com>,
"Wang, Yang(Kevin)" <KevinYang.Wang@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/amd/amdgpu: introduce DRM_AMDGPU_WERROR
Date: Tue, 30 May 2023 11:55:19 -0400 [thread overview]
Message-ID: <0f2021ba-fab9-3438-950d-7b60882ae77a@amd.com> (raw)
In-Reply-To: <DM6PR12MB3996064F09E1C2FD782CC944834B9@DM6PR12MB3996.namprd12.prod.outlook.com>
On 5/30/23 11:50, Ho, Kenny wrote:
> [Public]
>
> On 5/30/23 11:24, Hamza Mahfooz wrote:
>> I am able to get clean builds with this enabled on GCC 11-13 and Clang
>> 15, at least as of commit e786aef0869c ("drm/amd/display: remove unused
>> definition") on amd-staging-drm-next.
>
> Did you try intentionally introducing a warning to see if the build indeed fail?
Yes, I tried a couple of different ones.
--
Hamza
next prev parent reply other threads:[~2023-05-30 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 16:38 Hamza Mahfooz
2023-05-30 15:24 ` Hamza Mahfooz
2023-05-30 15:50 ` Ho, Kenny
2023-05-30 15:55 ` Hamza Mahfooz [this message]
2023-05-30 15:57 ` Ho, Kenny
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=0f2021ba-fab9-3438-950d-7b60882ae77a@amd.com \
--to=hamza.mahfooz@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Candice.Li@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=Hawking.Zhang@amd.com \
--cc=James.Zhu@amd.com \
--cc=Kenny.Ho@amd.com \
--cc=KevinYang.Wang@amd.com \
--cc=Le.Ma@amd.com \
--cc=Lijo.Lazar@amd.com \
--cc=Tao.Zhou1@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=YiPeng.Chai@amd.com \
--cc=afd@ti.com \
--cc=airlied@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrealmeid@igalia.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@pefoley.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®