From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jani Nikula" <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/params: fix i915.reset module param type
Date: Tue, 02 Jun 2020 15:34:55 -0000 [thread overview]
Message-ID: <159111209517.21427.12373126367453704843@emeril.freedesktop.org> (raw)
In-Reply-To: <20200602151126.25626-1-jani.nikula@intel.com>
== Series Details ==
Series: drm/i915/params: fix i915.reset module param type
URL : https://patchwork.freedesktop.org/series/77923/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
b693251369b3 drm/i915/params: fix i915.reset module param type
-:25: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#25: FILE: drivers/gpu/drm/i915/i915_params.c:78:
+i915_param_named_unsafe(reset, uint, 0400,
"Attempt GPU resets (0=disabled, 1=full gpu reset, 2=engine reset [default])");
total: 0 errors, 0 warnings, 1 checks, 8 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:[~2020-06-02 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 15:11 [Intel-gfx] [PATCH] drm/i915/params: fix i915.reset module param type Jani Nikula
2020-06-02 15:16 ` Chris Wilson
2020-06-04 9:31 ` Jani Nikula
2020-06-02 15:34 ` Patchwork [this message]
2020-06-02 15:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-06-02 23:05 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-06-03 15:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/params: fix i915.reset module param type (rev2) Patchwork
2020-06-03 15:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-06-04 4:50 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=159111209517.21427.12373126367453704843@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
/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).