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/gt: Ratelimit heartbeat completion probing (rev2)
Date: Thu, 04 Feb 2021 01:02:02 -0000 [thread overview]
Message-ID: <161240052232.4502.11252770103208463316@emeril.freedesktop.org> (raw)
In-Reply-To: <20210203210644.10163-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915/gt: Ratelimit heartbeat completion probing (rev2)
URL : https://patchwork.freedesktop.org/series/86665/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
8272367db0e5 drm/i915/gt: Ratelimit heartbeat completion probing
-:86: ERROR:CODE_INDENT: code indent should use tabs where possible
#86: FILE: drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c:86:
+^I ^Icontainer_of(cb, typeof(*engine), heartbeat.cb);$
-:86: WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#86: FILE: drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c:86:
+^I ^Icontainer_of(cb, typeof(*engine), heartbeat.cb);$
total: 1 errors, 1 warnings, 0 checks, 88 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-02-04 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 21:06 [Intel-gfx] [PATCH] drm/i915/gt: Ratelimit heartbeat completion probing Chris Wilson
2021-02-03 22:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-02-03 22:19 ` [Intel-gfx] [PATCH v2] " Chris Wilson
2021-02-03 22:46 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2021-02-04 1:02 ` Patchwork [this message]
2021-02-04 1:32 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gt: Ratelimit heartbeat completion probing (rev2) 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=161240052232.4502.11252770103208463316@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.