From: Christoph Hellwig <hch@infradead.org>
To: Hamza Mahfooz <hamza.mahfooz@amd.com>
Cc: amd-gfx@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Harry Wentland" <harry.wentland@amd.com>,
"Kenny Ho" <kenny.ho@amd.com>, "Leo Li" <sunpeng.li@amd.com>,
"Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/amd/display: enable more strict compile checks
Date: Thu, 25 May 2023 02:43:16 -0700 [thread overview]
Message-ID: <ZG8ttJ7VFrJCk8tB@infradead.org> (raw)
In-Reply-To: <20230524191955.252212-1-hamza.mahfooz@amd.com>
> +subdir-ccflags-y += -Werror -Wunused -Wmisleading-indentation
We have a config option for -Werror. Blindly adding this will create
problems with too new (or sometimes too old, or just too weird)
compilers all the time. Don't do this.
next prev parent reply other threads:[~2023-05-25 9:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 19:19 [PATCH v2] drm/amd/display: enable more strict compile checks Hamza Mahfooz
2023-05-24 19:22 ` Alex Deucher
2023-05-24 19:27 ` Hamza Mahfooz
2023-05-24 19:54 ` Harry Wentland
2023-05-24 19:57 ` Hamza Mahfooz
[not found] ` <DM6PR12MB3996C4248CBC968A7B08341583419@DM6PR12MB3996.namprd12.prod.outlook.com>
[not found] ` <BL1PR12MB589849F37FBE98A3A06A316185419@BL1PR12MB5898.namprd12.prod.outlook.com>
2023-05-24 19:45 ` Felix Kuehling
2023-05-24 19:50 ` Alex Deucher
2023-05-24 19:56 ` Ho, Kenny
2023-05-24 20:27 ` Hamza Mahfooz
2023-05-25 7:48 ` Jani Nikula
2023-05-25 15:37 ` Kees Cook
2023-05-25 16:26 ` Nathan Chancellor
2023-05-25 9:43 ` Christoph Hellwig [this message]
2023-05-26 5:00 ` kernel test robot
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=ZG8ttJ7VFrJCk8tB@infradead.org \
--to=hch@infradead.org \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamza.mahfooz@amd.com \
--cc=harry.wentland@amd.com \
--cc=kenny.ho@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sunpeng.li@amd.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