public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for RFT drm/i915/tgl: Re-enable rps (rev2)
Date: Tue, 01 Oct 2019 08:34:48 -0000	[thread overview]
Message-ID: <20191001083448.21995.58118@emeril.freedesktop.org> (raw)
In-Reply-To: <20190930123929.12758-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: RFT drm/i915/tgl: Re-enable rps (rev2)
URL   : https://patchwork.freedesktop.org/series/67398/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
c071a17cd8f9 RFT drm/i915/tgl: Re-enable rps
-:8: WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one

-:18: ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)

total: 1 errors, 1 warnings, 0 checks, 7 lines checked

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

  parent reply	other threads:[~2019-10-01  8:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30 12:39 [CI] RFT drm/i915/tgl: Re-enable rps Chris Wilson
2019-09-30 12:47 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-09-30 13:13 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-30 14:29 ` [CI] " Chris Wilson
2019-09-30 16:35 ` ✓ Fi.CI.IGT: success for " Patchwork
2019-10-01  8:34 ` Patchwork [this message]
2019-10-01  9:02 ` ✓ Fi.CI.BAT: success for RFT drm/i915/tgl: Re-enable rps (rev2) Patchwork
2019-10-01 11:50 ` ✓ Fi.CI.IGT: " Patchwork
2019-10-01 14:18 ` ✗ Fi.CI.CHECKPATCH: warning for RFT drm/i915/tgl: Re-enable rps (rev3) Patchwork
2019-10-01 14:54 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-01 22:18 ` ✓ 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=20191001083448.21995.58118@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --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