From: Patchwork <patchwork@emeril.freedesktop.org>
To: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for GuC suspend paths cleanup
Date: Wed, 20 Feb 2019 02:09:21 -0000 [thread overview]
Message-ID: <20190220020921.5011.46473@emeril.freedesktop.org> (raw)
In-Reply-To: <20190220013927.9488-1-sujaritha.sundaresan@intel.com>
== Series Details ==
Series: GuC suspend paths cleanup
URL : https://patchwork.freedesktop.org/series/56938/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
87b2a8a5132c drm/i915/guc: Splitting CT channel open/close functions
-:78: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#78: FILE: drivers/gpu/drm/i915/intel_guc_ct.c:218:
+static int ctch_enable(struct intel_guc *guc,
struct intel_guc_ct_channel *ctch)
-:128: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#128: FILE: drivers/gpu/drm/i915/intel_guc_ct.c:271:
+static void ctch_disable(struct intel_guc *guc,
struct intel_guc_ct_channel *ctch)
-:187: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#187: FILE: drivers/gpu/drm/i915/intel_guc_ct.c:863:
+ DRM_ERROR("CT: can't open channel %d; err=%d\n",
+ ctch->owner, err);
total: 0 errors, 0 warnings, 3 checks, 219 lines checked
16533d032f4f drm/i915/guc: Calling guc_disable_communication in all suspend paths
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-20 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 1:39 [PATCH v3 0/2] GuC suspend paths cleanup Sujaritha Sundaresan
2019-02-20 1:39 ` [PATCH v3 1/2] drm/i915/guc: Splitting CT channel open/close functions Sujaritha Sundaresan
2019-02-20 16:51 ` Daniele Ceraolo Spurio
2019-02-21 0:54 ` Chris Wilson
2019-02-20 1:39 ` [PATCH v3 2/2] drm/i915/guc: Calling guc_disable_communication in all suspend paths Sujaritha Sundaresan
2019-02-20 2:09 ` Patchwork [this message]
2019-02-20 2:34 ` ✓ Fi.CI.BAT: success for GuC suspend paths cleanup Patchwork
2019-02-20 4:55 ` ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-02-14 21:45 [PATCH 0/2] " Sujaritha Sundaresan
2019-02-14 23:09 ` ✗ Fi.CI.CHECKPATCH: warning 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=20190220020921.5011.46473@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--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