From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915/pmu: Do not assume fixed hrtimer period
Date: Mon, 04 Jun 2018 13:05:50 -0000 [thread overview]
Message-ID: <20180604130550.6499.84943@emeril.freedesktop.org> (raw)
In-Reply-To: <20180604125239.5856-1-tvrtko.ursulin@linux.intel.com>
== Series Details ==
Series: drm/i915/pmu: Do not assume fixed hrtimer period
URL : https://patchwork.freedesktop.org/series/44191/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9461f26f5ca1 drm/i915/pmu: Do not assume fixed hrtimer period
-:109: ERROR:CODE_INDENT: code indent should use tabs where possible
#109: FILE: drivers/gpu/drm/i915/i915_pmu.c:237:
+^I^I^I intel_gpu_freq(dev_priv, val),$
-:109: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#109: FILE: drivers/gpu/drm/i915/i915_pmu.c:237:
+ add_sample_mult(&dev_priv->pmu.sample[__I915_SAMPLE_FREQ_ACT],
+ intel_gpu_freq(dev_priv, val),
total: 1 errors, 0 warnings, 1 checks, 140 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-06-04 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 12:52 [PATCH] drm/i915/pmu: Do not assume fixed hrtimer period Tvrtko Ursulin
2018-06-04 12:59 ` Chris Wilson
2018-06-04 13:03 ` Chris Wilson
2018-06-04 15:01 ` Tvrtko Ursulin
2018-06-04 15:11 ` Chris Wilson
2018-06-05 8:51 ` Tvrtko Ursulin
2018-06-05 9:06 ` Chris Wilson
2018-06-05 11:35 ` Tvrtko Ursulin
2018-06-05 11:42 ` Chris Wilson
2018-06-04 13:05 ` Patchwork [this message]
2018-06-04 13:26 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-06-04 14:17 ` ✓ Fi.CI.IGT: " Patchwork
2018-06-05 10:57 ` ✗ Fi.CI.BAT: failure for drm/i915/pmu: Do not assume fixed hrtimer period (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=20180604130550.6499.84943@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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.