From: Patchwork <patchwork@emeril.freedesktop.org>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for CRTC background color (rev4)
Date: Sat, 29 Dec 2018 00:01:16 -0000 [thread overview]
Message-ID: <20181229000116.15052.40751@emeril.freedesktop.org> (raw)
In-Reply-To: <20181228235131.23465-1-matthew.d.roper@intel.com>
== Series Details ==
Series: CRTC background color (rev4)
URL : https://patchwork.freedesktop.org/series/50834/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
b53f08e7eb12 drm/i915: Force background color to black for gen9+ (v2)
2544c9624336 drm: Add CRTC background color property (v4)
-:218: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'shift' - possible side-effects?
#218: FILE: include/uapi/drm/drm_mode.h:931:
+#define DRM_ARGB_COMP(c, shift, numbits) \
+ (__u16)(((c) & 0xFFFFull << (shift)) >> ((shift) + 16 - (numbits)))
total: 0 errors, 0 warnings, 1 checks, 132 lines checked
720c678293f9 drm/i915/gen9+: Add support for pipe background color (v4)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-12-29 0:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 23:51 [PATCH v4 0/3] CRTC background color Matt Roper
2018-12-28 23:51 ` [PATCH v4 1/3] drm/i915: Force background color to black for gen9+ (v2) Matt Roper
2018-12-28 23:51 ` [PATCH v4 2/3] drm: Add CRTC background color property (v4) Matt Roper
2018-12-29 7:07 ` kbuild test robot
2019-01-07 11:08 ` Brian Starkey
2018-12-28 23:51 ` [PATCH v4 3/3] drm/i915/gen9+: Add support for pipe background color (v4) Matt Roper
2018-12-29 0:01 ` Patchwork [this message]
2018-12-29 0:26 ` ✓ Fi.CI.BAT: success for CRTC background color (rev4) Patchwork
2018-12-29 1:43 ` ✓ Fi.CI.IGT: " 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=20181229000116.15052.40751@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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 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.