From: Leandro Ribeiro <leandro.ribeiro@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: airlied@gmail.com, broonie@kernel.org, daniels@collabora.com,
jani.nikula@linux.intel.com, maarten.lankhorst@linux.intel.com,
miguel.ojeda.sandonis@gmail.com, mripard@kernel.org,
pekka.paalanen@collabora.com, simona@ffwll.ch,
penguin-kernel@I-love.SAKURA.ne.jp, tytso@mit.edu,
tzimmermann@suse.de, ville.syrjala@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] drm: use drm_warn() in validate_blend_mode_for_alpha_formats()
Date: Wed, 29 Jul 2026 18:45:04 -0300 [thread overview]
Message-ID: <20260729214505.185776-1-leandro.ribeiro@collabora.com> (raw)
This replaces a WARN() with drm_warn() in
validate_blend_mode_for_alpha_formats().
The condition is expected to be triggered by existing drivers while they
adapt to the new blend mode requirement, so it should not use the kernel
warning report mechanism. WARN() output can cause fuzzers to stop when
they encounter a "WARNING:" message.
drm_warn() keeps the warning visible to driver developers without
triggering a WARN().
Leandro Ribeiro (1):
drm: use drm_warn() in validate_blend_mode_for_alpha_formats()
drivers/gpu/drm/drm_mode_config.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.55.0
next reply other threads:[~2026-07-29 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 21:45 Leandro Ribeiro [this message]
2026-07-29 21:45 ` [PATCH 1/1] " Leandro Ribeiro
2026-07-29 22:13 ` Tetsuo Handa
2026-07-30 18:54 ` Leandro Ribeiro
2026-07-30 23:14 ` Tetsuo Handa
2026-07-30 23:18 ` Leandro Ribeiro
2026-07-30 9:14 ` Jani Nikula
2026-07-30 18:46 ` Leandro Ribeiro
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=20260729214505.185776-1-leandro.ribeiro@collabora.com \
--to=leandro.ribeiro@collabora.com \
--cc=airlied@gmail.com \
--cc=broonie@kernel.org \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mripard@kernel.org \
--cc=pekka.paalanen@collabora.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=simona@ffwll.ch \
--cc=tytso@mit.edu \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.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®