From: Patchwork <patchwork@emeril.freedesktop.org>
To: Stuart Summers <stuart.summers@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for Add module parameter to reduce engine instances
Date: Tue, 27 Aug 2019 23:21:10 -0000 [thread overview]
Message-ID: <20190827232110.24240.26482@emeril.freedesktop.org> (raw)
In-Reply-To: <20190827231435.398-1-stuart.summers@intel.com>
== Series Details ==
Series: Add module parameter to reduce engine instances
URL : https://patchwork.freedesktop.org/series/65900/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
7377558e7eee drm/i915: WARN rather than BUG with unexpected media engines
43af249229a9 drm/i915: Add ring_mask module parameter
-:22: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#22: FILE: drivers/gpu/drm/i915/i915_params.c:182:
+i915_param_named_unsafe(ring_mask, uint, 0400,
+ "Mask of engine rings to enable. (default: all supported engines enabled)");
total: 0 errors, 0 warnings, 1 checks, 34 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:[~2019-08-27 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 23:14 [PATCH 0/2] Add module parameter to reduce engine instances Stuart Summers
2019-08-27 23:14 ` [PATCH 1/2] drm/i915: WARN rather than BUG with unexpected media engines Stuart Summers
2019-08-27 23:14 ` [PATCH 2/2] drm/i915: Add ring_mask module parameter Stuart Summers
2019-08-28 9:34 ` Chris Wilson
2019-08-28 15:13 ` Summers, Stuart
2019-08-27 23:21 ` Patchwork [this message]
2019-08-28 9:28 ` ✓ Fi.CI.BAT: success for Add module parameter to reduce engine instances Patchwork
2019-08-29 10:16 ` ✓ 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=20190827232110.24240.26482@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stuart.summers@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