From: Patchwork <patchwork@emeril.freedesktop.org>
To: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915/frontbuffer: Pull frontbuffer_flush out of gem_obj_pin_to_display
Date: Fri, 16 Feb 2018 04:38:40 -0000 [thread overview]
Message-ID: <20180216043840.20193.3314@emeril.freedesktop.org> (raw)
In-Reply-To: <20180216043322.22874-1-dhinakaran.pandiyan@intel.com>
== Series Details ==
Series: series starting with [1/5] drm/i915/frontbuffer: Pull frontbuffer_flush out of gem_obj_pin_to_display
URL : https://patchwork.freedesktop.org/series/38410/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
28b7f4f93d2f drm/i915/frontbuffer: Pull frontbuffer_flush out of gem_obj_pin_to_display
8721f68002db drm/i915/psr: Use more PSR HW tracking.
-:65: WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
#65: FILE: drivers/gpu/drm/i915/intel_drv.h:1865:
+ unsigned frontbuffer_bits,
-:100: WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
#100: FILE: drivers/gpu/drm/i915/intel_psr.c:837:
+ unsigned frontbuffer_bits, enum fb_op_origin origin)
total: 0 errors, 2 warnings, 0 checks, 64 lines checked
787bd9dab50d drm/i915/frontbuffer: HW tracking for cursor moves to fix PSR lags.
478be48e1ec8 drm/i915/frontbuffer: Remove early frontbuffer flush in prepare_plane_fb()
c1b5cfe64bc4 drm/i915/psr: Wait for PSR transition to complete before exiting.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-16 4:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 4:33 [PATCH 1/5] drm/i915/frontbuffer: Pull frontbuffer_flush out of gem_obj_pin_to_display Dhinakaran Pandiyan
2018-02-16 4:33 ` [PATCH 2/5] drm/i915/psr: Use more PSR HW tracking Dhinakaran Pandiyan
2018-02-16 8:54 ` Chris Wilson
2018-03-07 3:54 ` Pandiyan, Dhinakaran
2018-02-16 4:33 ` [PATCH 3/5] drm/i915/frontbuffer: HW tracking for cursor moves to fix PSR lags Dhinakaran Pandiyan
2018-02-16 4:33 ` [PATCH 4/5] drm/i915/frontbuffer: Remove early frontbuffer flush in prepare_plane_fb() Dhinakaran Pandiyan
2018-02-16 8:55 ` Chris Wilson
2018-02-16 19:27 ` Pandiyan, Dhinakaran
2018-02-19 9:07 ` Maarten Lankhorst
2018-02-24 3:24 ` Pandiyan, Dhinakaran
2018-02-28 20:28 ` Ville Syrjälä
2018-02-28 20:38 ` Ville Syrjälä
2018-02-28 23:38 ` Pandiyan, Dhinakaran
2018-03-01 10:51 ` Ville Syrjälä
2018-03-01 11:22 ` Ville Syrjälä
2018-03-01 18:35 ` Rodrigo Vivi
2018-03-01 18:43 ` Ville Syrjälä
2018-03-01 19:00 ` Rodrigo Vivi
2018-03-01 19:21 ` Pandiyan, Dhinakaran
2018-03-01 19:24 ` Ville Syrjälä
2018-02-16 4:33 ` [PATCH 5/5] drm/i915/psr: Wait for PSR transition to complete before exiting Dhinakaran Pandiyan
2018-02-16 8:58 ` Chris Wilson
2018-02-16 18:58 ` Pandiyan, Dhinakaran
2018-02-16 4:38 ` Patchwork [this message]
2018-02-16 4:54 ` ✓ Fi.CI.BAT: success for series starting with [1/5] drm/i915/frontbuffer: Pull frontbuffer_flush out of gem_obj_pin_to_display Patchwork
2018-02-16 8:52 ` [PATCH 1/5] " Chris Wilson
2018-02-16 19:22 ` Pandiyan, Dhinakaran
2018-02-16 11:55 ` ✓ Fi.CI.IGT: success for series starting with [1/5] " 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=20180216043840.20193.3314@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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