From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Bhanuprakash Modem" <bhanuprakash.modem@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Expose crtc dither state and connector max bpc via debugfs (rev2)
Date: Mon, 20 Jul 2020 12:16:19 -0000 [thread overview]
Message-ID: <159524737938.13114.7349869682463538682@emeril.freedesktop.org> (raw)
In-Reply-To: <20200720194127.24750-1-bhanuprakash.modem@intel.com>
== Series Details ==
Series: Expose crtc dither state and connector max bpc via debugfs (rev2)
URL : https://patchwork.freedesktop.org/series/79664/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
525ee1f3c796 i915/debug: Expose crtc dither state via debugfs
-:45: WARNING:SYMBOLIC_PERMS: Symbolic permissions 'S_IRUGO' are not preferred. Consider using octal permissions '0444'.
#45: FILE: drivers/gpu/drm/i915/i915_debugfs.c:1674:
+ debugfs_create_file("dither", S_IRUGO, crtc->debugfs_entry, crtc,
-:46: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#46: FILE: drivers/gpu/drm/i915/i915_debugfs.c:1675:
+ debugfs_create_file("dither", S_IRUGO, crtc->debugfs_entry, crtc,
+ &dither_state_fops);
total: 0 errors, 1 warnings, 1 checks, 30 lines checked
7d1f9ca422bf i915/debug: Expose Max BPC info via debugfs
-:46: WARNING:SYMBOLIC_PERMS: Symbolic permissions 'S_IRUGO' are not preferred. Consider using octal permissions '0444'.
#46: FILE: drivers/gpu/drm/i915/display/intel_display_debugfs.c:2252:
+ debugfs_create_file("output_bpc", S_IRUGO, root,
-:47: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#47: FILE: drivers/gpu/drm/i915/display/intel_display_debugfs.c:2253:
+ debugfs_create_file("output_bpc", S_IRUGO, root,
+ connector, &output_bpc_fops);
total: 0 errors, 1 warnings, 1 checks, 28 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-07-20 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 19:41 [Intel-gfx] [PATCH 0/2] Expose crtc dither state and connector max bpc via debugfs Bhanuprakash Modem
2020-07-20 12:16 ` Patchwork [this message]
2020-07-20 12:16 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Expose crtc dither state and connector max bpc via debugfs (rev2) Patchwork
2020-07-20 12:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-07-20 15:08 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-07-20 19:41 ` [Intel-gfx] [PATCH 1/2] i915/debug: Expose crtc dither state via debugfs Bhanuprakash Modem
2020-07-20 19:41 ` [Intel-gfx] [PATCH 2/2] i915/debug: Expose Max BPC info " Bhanuprakash Modem
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=159524737938.13114.7349869682463538682@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=bhanuprakash.modem@intel.com \
--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 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.