summaryrefslogtreecommitdiff
path: root/scripts/const_structs.checkpatch
diff options
context:
space:
mode:
authorLeandro Ribeiro <leandro.ribeiro@collabora.com>2026-07-31 12:42:32 -0300
committerDaniel Stone <daniels@collabora.com>2026-08-14 14:43:23 +0100
commit271e90eb5f9ff34951647e5ed33c1775eebcca50 (patch)
treeafe123b6cf737c40ba35e5e69b1f8c6cd52fb5c6 /scripts/const_structs.checkpatch
parent651b0bd0922b265c6c58d9dc84ef3fd00782a0cd (diff)
downloadlinux-271e90eb5f9ff34951647e5ed33c1775eebcca50.tar.gz
linux-271e90eb5f9ff34951647e5ed33c1775eebcca50.zip
drm: use drm_warn() in validate_blend_mode_for_alpha_formats()
Commit 860e748bddcc ("drm: ensure blend mode supported if pixel format with alpha exposed") introduced a WARN() to let driver developers know that a previously valid behavior should now be changed. But WARN() should not be used for that, as it's a kernel warning report mechanism for conditions that are not expected to happen. It also produces a stack trace. Instead, a simple warning-level log message should have been used, as drivers were expected to trigger the condition. This is causing problems for fuzzers, as they may stop when encountering a "BUG:" or "WARNING:" in the logs. Replace WARN() with drm_warn() in this function, avoiding these issues. Fixes: 860e748bddcc ("drm: ensure blend mode supported if pixel format with alpha exposed") Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Link: https://patch.msgid.link/20260731154232.37020-2-leandro.ribeiro@collabora.com Signed-off-by: Daniel Stone <daniels@collabora.com>
Diffstat (limited to 'scripts/const_structs.checkpatch')
0 files changed, 0 insertions, 0 deletions