All of lore.kernel.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: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt:fix raw-wakeref not held calltrace in vGPU (rev2)
Date: Tue, 11 Aug 2020 10:29:25 -0000	[thread overview]
Message-ID: <159714176507.3768.602448425941641231@emeril.freedesktop.org> (raw)
In-Reply-To: <20200811030209.21058-1-yan.y.zhao@intel.com>

== Series Details ==

Series: drm/i915/gt:fix raw-wakeref not held calltrace in vGPU (rev2)
URL   : https://patchwork.freedesktop.org/series/80497/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
ecbbc5815c0f drm/i915: Drop runtime-pm assert from vgpu io accessors
-:16: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#16: 
References: 3be0bf5acca6 ("drm/i915: Create vGPU specific MMIO operations to reduce traps")

-:16: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 3be0bf5acca6 ("drm/i915: Create vGPU specific MMIO operations to reduce traps")'
#16: 
References: 3be0bf5acca6 ("drm/i915: Create vGPU specific MMIO operations to reduce traps")

-:29: ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#29: FILE: drivers/gpu/drm/i915/intel_uncore.c:1212:
+#define __vgpu_read(x) \
+static u##x \
+vgpu_read##x(struct intel_uncore *uncore, i915_reg_t reg, bool trace) { \
+	u##x val = __raw_uncore_read##x(uncore, reg); \
+	trace_i915_reg_rw(false, reg, val, sizeof(val), trace); \
+	return val; \
+}

-:36: CHECK:LINE_SPACING: Please use a blank line after function/struct/union/enum declarations
#36: FILE: drivers/gpu/drm/i915/intel_uncore.c:1219:
+}
+__vgpu_read(8)

-:54: CHECK:LINE_SPACING: Please use a blank line after function/struct/union/enum declarations
#54: FILE: drivers/gpu/drm/i915/intel_uncore.c:1435:
+}
+__vgpu_write(8)

total: 2 errors, 1 warnings, 2 checks, 45 lines checked


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

  parent reply	other threads:[~2020-08-11 10:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  3:02 [Intel-gfx] [PATCH] drm/i915/gt:fix raw-wakeref not held calltrace in vGPU Yan Zhao
2020-08-11  3:57 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2020-08-11  4:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-08-11  5:38 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-08-11  8:26 ` [Intel-gfx] [PATCH] " Chris Wilson
2020-08-11  8:18   ` Yan Zhao
2020-08-11  8:39   ` Zhenyu Wang
2020-08-11  9:25 ` [Intel-gfx] [PATCH] drm/i915: Drop runtime-pm assert from vgpu io accessors Chris Wilson
2020-08-12  2:06   ` Zhenyu Wang
2020-08-19  8:32     ` Zhenyu Wang
2020-10-19  9:37       ` Zhenyu Wang
2020-10-20  9:41         ` Chris Wilson
2020-08-11 10:29 ` Patchwork [this message]
2020-08-11 10:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt:fix raw-wakeref not held calltrace in vGPU (rev2) Patchwork
2020-08-11 13:25 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=159714176507.3768.602448425941641231@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.