From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Bump the scheduling threshold for fast heartbeats (rev3)
Date: Wed, 13 Jan 2021 18:34:16 -0000 [thread overview]
Message-ID: <161056285626.11118.15744514050957298016@emeril.freedesktop.org> (raw)
In-Reply-To: <20210113125155.1029-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915/selftests: Bump the scheduling threshold for fast heartbeats (rev3)
URL : https://patchwork.freedesktop.org/series/85804/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
752b57baab51 drm/i915/selftests: Bump the scheduling error threshold for fast heartbeats
-:15: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#15:
<3> [616.859296] vcs0: Heartbeat delay was 6485us, expected less than 6000us
total: 0 errors, 1 warnings, 0 checks, 28 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:[~2021-01-13 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 12:51 [Intel-gfx] [PATCH] drm/i915/selftests: Bump the scheduling threshold for fast heartbeats Chris Wilson
2021-01-13 12:59 ` Chris Wilson
2021-01-13 14:13 ` Mika Kuoppala
2021-01-13 14:20 ` Chris Wilson
2021-01-13 14:23 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/selftests: Bump the scheduling threshold for fast heartbeats (rev2) Patchwork
2021-01-13 14:45 ` [Intel-gfx] [PATCH v2] drm/i915/selftests: Bump the scheduling error threshold for fast heartbeats Chris Wilson
2021-01-13 16:00 ` Mika Kuoppala
2021-01-13 18:34 ` Patchwork [this message]
2021-01-13 19:04 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/selftests: Bump the scheduling threshold for fast heartbeats (rev3) 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=161056285626.11118.15744514050957298016@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;
as well as URLs for NNTP newsgroup(s).