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 Use intel_* types more consistently
Date: Fri, 07 Dec 2018 01:09:57 -0000 [thread overview]
Message-ID: <20181207010957.2790.72435@emeril.freedesktop.org> (raw)
In-Reply-To: <20181207005401.13988-1-matthew.d.roper@intel.com>
== Series Details ==
Series: Use intel_* types more consistently
URL : https://patchwork.freedesktop.org/series/53705/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3b3378ade6f9 drm/i915: Use intel_ types more consistently for watermark code
3c31c0ac3fda drm/i915: Use intel_ types more consistently for color management code
-:209: CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around 'state->gamma_mode == GAMMA_MODE_MODE_SPLIT'
#209: FILE: drivers/gpu/drm/i915/intel_color.c:367:
+ if (IS_HASWELL(dev_priv) && state->ips_enabled &&
+ (state->gamma_mode == GAMMA_MODE_MODE_SPLIT)) {
total: 0 errors, 0 warnings, 1 checks, 511 lines checked
_______________________________________________
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-07 1:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 0:53 [PATCH 0/2] Use intel_* types more consistently Matt Roper
2018-12-07 0:54 ` [PATCH 1/2] drm/i915: Use intel_ types more consistently for watermark code Matt Roper
2018-12-10 19:27 ` Ville Syrjälä
2018-12-07 0:54 ` [PATCH 2/2] drm/i915: Use intel_ types more consistently for color management code Matt Roper
2018-12-10 19:31 ` Ville Syrjälä
2018-12-10 23:07 ` Matt Roper
2018-12-07 1:09 ` Patchwork [this message]
2018-12-07 1:11 ` ✗ Fi.CI.SPARSE: warning for Use intel_* types more consistently Patchwork
2018-12-07 1:31 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-07 13:47 ` ✓ 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=20181207010957.2790.72435@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox