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 drm/i915: Update kerneldoc for intel_wm_need_update()
Date: Mon, 31 Dec 2018 14:44:49 -0000 [thread overview]
Message-ID: <20181231144449.26495.79262@emeril.freedesktop.org> (raw)
In-Reply-To: <20181231143505.2523-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915: Update kerneldoc for intel_wm_need_update()
URL : https://patchwork.freedesktop.org/series/54588/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a01df540d414 drm/i915: Update kerneldoc for intel_wm_need_update()
-:14: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#14:
References: cd1d3ee90e5e ("drm/i915: Use intel_ types more consistently for watermark code (v2)")
-:14: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit cd1d3ee90e5e ("drm/i915: Use intel_ types more consistently for watermark code (v2)")'
#14:
References: cd1d3ee90e5e ("drm/i915: Use intel_ types more consistently for watermark code (v2)")
total: 1 errors, 1 warnings, 0 checks, 10 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-31 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 14:35 [PATCH] drm/i915: Update kerneldoc for intel_wm_need_update() Chris Wilson
2018-12-31 14:44 ` Patchwork [this message]
2018-12-31 15:04 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-12-31 15:05 ` [PATCH] " Tvrtko Ursulin
2018-12-31 17:03 ` ✓ Fi.CI.IGT: success for " 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=20181231144449.26495.79262@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.