From: Patchwork <patchwork@emeril.freedesktop.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915: add support for specifying DMC firmware override by module param (rev3)
Date: Tue, 24 Apr 2018 13:46:01 -0000 [thread overview]
Message-ID: <20180424134601.19892.257@emeril.freedesktop.org> (raw)
In-Reply-To: <20180424122016.2416-1-jani.nikula@intel.com>
== Series Details ==
Series: drm/i915: add support for specifying DMC firmware override by module param (rev3)
URL : https://patchwork.freedesktop.org/series/34157/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c62c2ab8334b drm/i915: add support for specifying DMC firmware override by module param
-:27: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#27: FILE: drivers/gpu/drm/i915/i915_params.c:168:
+i915_param_named_unsafe(dmc_firmware_path, charp, 0400,
+ "DMC firmware path to use instead of the default one");
total: 0 errors, 0 warnings, 1 checks, 37 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-04-24 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 12:20 [PATCH v2 RESEND] drm/i915: add support for specifying DMC firmware override by module param Jani Nikula
2018-04-24 13:46 ` Patchwork [this message]
2018-04-24 14:01 ` ✓ Fi.CI.BAT: success for drm/i915: add support for specifying DMC firmware override by module param (rev3) Patchwork
2018-04-24 17:44 ` ✓ Fi.CI.IGT: " Patchwork
2018-04-27 14:08 ` [PATCH v2 RESEND] drm/i915: add support for specifying DMC firmware override by module param David Weinehall
2018-04-30 10:47 ` Jani Nikula
2018-04-30 12:45 ` David Weinehall
2018-04-30 18:00 ` Srivatsa, Anusha
2018-04-30 18:14 ` Srivatsa, Anusha
2018-05-02 10:13 ` Jani Nikula
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=20180424134601.19892.257@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 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.