From: Patchwork <patchwork@emeril.freedesktop.org>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add psr_safest_params
Date: Wed, 20 May 2020 22:10:19 -0000 [thread overview]
Message-ID: <159001261935.30688.5307549845807009493@emeril.freedesktop.org> (raw)
In-Reply-To: <20200520212756.354623-1-jose.souza@intel.com>
== Series Details ==
Series: drm/i915: Add psr_safest_params
URL : https://patchwork.freedesktop.org/series/77491/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
7f3095d8f257 drm/i915: Add psr_safest_params
-:98: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#98: FILE: drivers/gpu/drm/i915/i915_params.c:92:
+i915_param_named(psr_safest_params, bool, 0400,
+ "Replace PSR VBT parameters by the safest and not optimal ones. This "
-:99: WARNING:TYPO_SPELLING: 'helpfull' may be misspelled - perhaps 'helpful'?
#99: FILE: drivers/gpu/drm/i915/i915_params.c:93:
+ "is helpfull to detect if PSR issues are related to bad values set in "
-:100: WARNING:TYPO_SPELLING: 'paramters' may be misspelled - perhaps 'parameters'?
#100: FILE: drivers/gpu/drm/i915/i915_params.c:94:
+ " VBT. (0=use VBT paramters, 1=use safest parameters)");
total: 0 errors, 2 warnings, 1 checks, 82 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-05-20 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 21:27 [Intel-gfx] [PATCH] drm/i915: Add psr_safest_params José Roberto de Souza
2020-05-20 22:10 ` Patchwork [this message]
2020-05-20 22:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-05-21 16:04 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-06-05 2:40 ` Souza, Jose
2020-06-04 23:38 ` [Intel-gfx] [PATCH] " Mun, Gwan-gyeong
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=159001261935.30688.5307549845807009493@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@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).