Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm: avoid spurious EBUSY due to nonblocking atomic modesets
Date: Thu, 05 Jul 2018 10:25:18 -0000	[thread overview]
Message-ID: <20180705102518.21738.4967@emeril.freedesktop.org> (raw)
In-Reply-To: <20180705101043.4883-1-daniel.vetter@ffwll.ch>

== Series Details ==

Series: drm: avoid spurious EBUSY due to nonblocking atomic modesets
URL   : https://patchwork.freedesktop.org/series/45968/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
ae0e8aaf3ac4 drm: avoid spurious EBUSY due to nonblocking atomic modesets
-:33: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#33: 
References: https://lists.freedesktop.org/archives/dri-devel/2018-July/182281.html

-:49: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#49: FILE: drivers/gpu/drm/drm_atomic.c:2021:
+	unsigned requested_crtc = 0;

-:50: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#50: FILE: drivers/gpu/drm/drm_atomic.c:2022:
+	unsigned affected_crtc = 0;

total: 0 errors, 3 warnings, 0 checks, 46 lines checked

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-07-05 10:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05 10:10 [PATCH] drm: avoid spurious EBUSY due to nonblocking atomic modesets Daniel Vetter
2018-07-05 10:21 ` Daniel Vetter
2020-01-31  7:34   ` [Intel-gfx] " Daniel Stone
2020-09-22 13:36     ` Marius Vlad
2020-09-22 14:04       ` Daniel Vetter
2020-09-22 14:14         ` Daniel Stone
2020-09-22 16:01           ` Daniel Vetter
2020-09-22 19:02             ` Daniel Stone
2020-09-23 10:58       ` Daniel Vetter
2020-09-23 11:14         ` Marius Vlad
2020-09-23 11:16           ` Daniel Vetter
2020-09-23 11:31             ` Marius Vlad
2018-07-05 10:25 ` Patchwork [this message]
2018-07-05 10:41 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-07-05 10:45 ` ✗ Fi.CI.CHECKPATCH: warning for drm: avoid spurious EBUSY due to nonblocking atomic modesets (rev2) Patchwork
2018-07-05 11:01 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-05 12:23 ` ✗ Fi.CI.IGT: failure " 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=20180705102518.21738.4967@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=daniel.vetter@ffwll.ch \
    --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