From: Ian Rogers <irogers@google.com>
To: Lyude Paul <lyude@redhat.com>, Danilo Krummrich <dakr@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
Elkin Cruz <elkin@google.com>, Ian Rogers <irogers@google.com>
Subject: [PATCH 0/2] drm/nouveau: Two fixes from Clang warning audit
Date: Thu, 19 Nov 2026 09:03:56 -0800 [thread overview]
Message-ID: <cover.1795106937.git.irogers@google.com> (raw)
Two independent fixes in drm/nouveau found while auditing Clang
warnings (-Wswitch-enum and -Wconditional-uninitialized) on an
x86_64 allyesconfig build:
1. Handle NVIF_CONN_TV and release nv_connector on error in
nouveau_connector_create().
2. Initialize primary_crc before switching on src in
crcca7d_get_crc() for GB20x RG CRC capture.
Build-tested with LLVM=1 W=1 (-Werror); not runtime-tested on
Nouveau hardware.
Ian Rogers (2):
drm/nouveau: Handle NVIF_CONN_TV and fix error cleanup in
nouveau_connector_create()
drm/nouveau/kms: Initialize primary_crc for RG CRC capture on GB20x
drivers/gpu/drm/nouveau/dispnv50/crcca7d.c | 1 +
drivers/gpu/drm/nouveau/nouveau_connector.c | 7 ++++++-
2 files changed, 7 insertions(+), 1 deletion(-)
--
2.56.1.708.g77570a6a1d-goog
next reply other threads:[~2026-11-19 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 17:03 Ian Rogers [this message]
2026-11-19 17:03 ` [PATCH 1/2] drm/nouveau: Handle NVIF_CONN_TV and fix error cleanup in nouveau_connector_create() Ian Rogers
2026-11-19 17:03 ` [PATCH 2/2] drm/nouveau/kms: Initialize primary_crc for RG CRC capture on GB20x Ian Rogers
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.1795106937.git.irogers@google.com \
--to=irogers@google.com \
--cc=airlied@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=elkin@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
--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