From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/atomic: Use explicit old crtc state in drm_atomic_add_affected_planes() (rev2)
Date: Wed, 07 Nov 2018 13:04:36 -0000 [thread overview]
Message-ID: <20181107130436.31413.61306@emeril.freedesktop.org> (raw)
In-Reply-To: <20181101184646.14753-1-ville.syrjala@linux.intel.com>
== Series Details ==
Series: series starting with [1/3] drm/atomic: Use explicit old crtc state in drm_atomic_add_affected_planes() (rev2)
URL : https://patchwork.freedesktop.org/series/51894/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e5ec4f59a037 drm/atomic: Use explicit old crtc state in drm_atomic_add_affected_planes()
1bfa9185dee8 drm/atomic: Use explicit old/new state in drm_atomic_crtc_check()
f6d1a322301f drm/atomic: Use explicit old/new state in drm_atomic_plane_check()
-:118: CHECK:SPACING: No space is necessary after a cast
#118: FILE: drivers/gpu/drm/drm_atomic.c:574:
+ new_plane_state->crtc_x > INT_MAX - (int32_t) new_plane_state->crtc_w ||
-:120: CHECK:SPACING: No space is necessary after a cast
#120: FILE: drivers/gpu/drm/drm_atomic.c:576:
+ new_plane_state->crtc_y > INT_MAX - (int32_t) new_plane_state->crtc_h) {
total: 0 errors, 0 warnings, 2 checks, 163 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-11-07 13:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 18:46 [PATCH 1/3] drm/atomic: Use explicit old crtc state in drm_atomic_add_affected_planes() Ville Syrjala
2018-11-01 18:46 ` [PATCH 2/3] drm/atomic: Use explicit old/new state in drm_atomic_crtc_check() Ville Syrjala
2018-11-05 9:29 ` Daniel Vetter
2018-11-01 18:46 ` [PATCH 3/3] drm/atomic: Use explicit old/new state in drm_atomic_plane_check() Ville Syrjala
2018-11-05 9:33 ` Daniel Vetter
2018-11-05 14:37 ` [Intel-gfx] " Ville Syrjälä
2018-11-06 19:16 ` [PATCH v2 " Ville Syrjala
2018-11-01 19:27 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/atomic: Use explicit old crtc state in drm_atomic_add_affected_planes() Patchwork
2018-11-01 19:45 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-02 0:05 ` ✓ Fi.CI.IGT: " Patchwork
2018-11-05 9:26 ` [PATCH 1/3] " Daniel Vetter
2018-11-05 14:04 ` Ville Syrjälä
2018-11-05 14:30 ` Wentland, Harry
2018-11-05 14:39 ` Ville Syrjälä
2018-11-07 13:04 ` Patchwork [this message]
2018-11-07 13:20 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/atomic: Use explicit old crtc state in drm_atomic_add_affected_planes() (rev2) Patchwork
2018-11-07 16:12 ` ✓ Fi.CI.IGT: " Patchwork
2018-11-07 17:47 ` 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=20181107130436.31413.61306@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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