From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
jani.nikula@intel.com
Subject: [PATCH v3 0/2] drm: enable W=1 warnings by default across the subsystem
Date: Thu, 1 Feb 2024 16:33:07 +0200 [thread overview]
Message-ID: <cover.1706797803.git.jani.nikula@intel.com> (raw)
This is v3 of [1], with the warning fixes already merged, and rebased on
upstream warning changes.
I built this on x86-64 (both gcc and clang), arm and arm64, and
everything passed.
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1704908087.git.jani.nikula@intel.com
Jani Nikula (2):
drm: enable (most) W=1 warnings by default across the subsystem
drm: Add CONFIG_DRM_WERROR
drivers/gpu/drm/Kconfig | 13 +++++++++++++
drivers/gpu/drm/Makefile | 28 ++++++++++++++++++++++++++++
2 files changed, 41 insertions(+)
--
2.39.2
next reply other threads:[~2024-02-01 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 14:33 Jani Nikula [this message]
2024-02-01 14:33 ` [PATCH v3 1/2] drm: enable (most) W=1 warnings by default across the subsystem Jani Nikula
2024-02-01 14:37 ` Danilo Krummrich
2024-02-01 14:33 ` [PATCH v3 2/2] drm: Add CONFIG_DRM_WERROR Jani Nikula
2024-02-01 14:36 ` ✓ CI.Patch_applied: success for drm: enable W=1 warnings by default across the subsystem Patchwork
2024-02-01 14:36 ` ✓ CI.checkpatch: " Patchwork
2024-02-01 14:37 ` ✓ CI.KUnit: " Patchwork
2024-02-01 14:44 ` ✓ CI.Build: " Patchwork
2024-02-01 14:45 ` ✓ CI.Hooks: " Patchwork
2024-02-01 14:46 ` ✗ CI.checksparse: warning " Patchwork
2024-02-01 15:10 ` ✓ CI.BAT: success " Patchwork
2024-02-01 15:34 ` ✗ Fi.CI.SPARSE: warning for drm: enable W=1 warnings by default across the subsystem (rev3) Patchwork
2024-02-01 16:14 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-01 18:10 ` ✗ Fi.CI.IGT: failure " Patchwork
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=cover.1706797803.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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 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.