From: Jani Nikula <jani.nikula@intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
Maxime Ripard <mripard@kernel.org>
Cc: Pan@freedesktop.org, "Karol Herbst" <kherbst@redhat.com>,
intel-gfx@lists.freedesktop.org, Xinhui <Xinhui.Pan@amd.com>,
"Abhinav Kumar" <quic_abhinavk@quicinc.com>,
dri-devel@lists.freedesktop.org,
"Nathan Chancellor" <nathan@kernel.org>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Danilo Krummrich" <dakr@redhat.com>,
"Hamza Mahfooz" <hamza.mahfooz@amd.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [Intel-gfx] [RFC] drm: enable W=1 warnings by default across the subsystem
Date: Thu, 30 Nov 2023 11:46:00 +0200 [thread overview]
Message-ID: <87y1ef4lrb.fsf@intel.com> (raw)
In-Reply-To: <87zfyva8qg.fsf@minerva.mail-host-address-is-not-set>
On Thu, 30 Nov 2023, Javier Martinez Canillas <javierm@redhat.com> wrote:
> Maxime Ripard <mripard@kernel.org> writes:
>
>> Hi,
>>
>> On Thu, Nov 30, 2023 at 10:52:17AM +0200, Jani Nikula wrote:
>>> On Wed, 29 Nov 2023, Hamza Mahfooz <hamza.mahfooz@amd.com> wrote:
>>> > Cc: Nathan Chancellor <nathan@kernel.org>
>>> >
>>> > On 11/29/23 13:12, Jani Nikula wrote:
>>> >> At least the i915 and amd drivers enable a bunch more compiler warnings
>>> >> than the kernel defaults.
>>> >>
>>> >> Extend the W=1 warnings to the entire drm subsystem by default. Use the
>>> >> copy-pasted warnings from scripts/Makefile.extrawarn with
>>> >> s/KBUILD_CFLAGS/subdir-ccflags-y/ to make it easier to compare and keep
>>> >> up with them in the future.
>>> >>
>>> >> This is similar to the approach currently used in i915.
>>> >>
>>> >> Some of the -Wextra warnings do need to be disabled, just like in
>>> >> Makefile.extrawarn, but take care to not disable them for W=2 or W=3
>>> >> builds, depending on the warning.
>>> >
>>> > I think this should go in after drm-misc-next has a clean build (for
>>> > COMPILE_TEST builds) with this patch applied. Otherwise, it will break a
>>> > lot of build configs.
>>>
>>> Oh, I'm absolutely not suggesting this should be merged before known
>>> warnings have been addressed one way or another. Either by fixing them
>>> or by disabling said warning in driver local Makefiles, depending on the
>>> case.
>>
>> I'm all for it, but yeah, we need some easy way to opt-in/opt-out. Some
>> drivers are pretty much unmaintained now and are likely to never fix
>> those warnings.
Then I'd go for enabling in drm level and disabling individual warnings
in the driver Makefile level if they won't get fixed.
> Maybe add a Kconfig symbol for it instead of making unconditional?
>
> Something like:
>
> +# Unconditionally enable W=1 warnings locally
> +# --- begin copy-paste W=1 warnings from scripts/Makefile.extrawarn
> +subdir-ccflags-$(CONFIG_DRM_EXTRA_CHECKS) += -Wextra -Wunused -Wno-unused-parameter
> ...
Then we'll have a ping pong of people not using W=1 or
CONFIG_DRM_EXTRA_CHECKS introducing warnings, and people using them
fixing the warnings...
I really do think making it unconditional is the only way.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-11-30 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 18:12 [Intel-gfx] [RFC] drm: enable W=1 warnings by default across the subsystem Jani Nikula
2023-11-29 20:21 ` Hamza Mahfooz
2023-11-30 8:52 ` Jani Nikula
2023-11-30 9:18 ` Maxime Ripard
2023-11-30 9:30 ` Javier Martinez Canillas
2023-11-30 9:46 ` Jani Nikula [this message]
2023-11-30 9:59 ` Javier Martinez Canillas
2023-11-30 10:06 ` Maxime Ripard
2023-11-30 10:19 ` Javier Martinez Canillas
2023-12-05 14:25 ` Dmitry Baryshkov
2023-12-01 17:59 ` Nathan Chancellor
2023-11-30 5:59 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-11-30 6:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-30 10:01 ` [Intel-gfx] [RFC] " Thomas Zimmermann
2023-12-01 6:15 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2023-12-05 14:08 ` [Intel-gfx] [RFC] " Sui Jingfeng
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=87y1ef4lrb.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=Pan@freedesktop.org \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=dakr@redhat.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamza.mahfooz@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=kherbst@redhat.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=tzimmermann@suse.de \
/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