From: Patchwork <patchwork@emeril.freedesktop.org>
To: Mahesh Kumar <mahesh1.kumar@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for Improve crc-core driver interface
Date: Fri, 22 Jun 2018 10:46:52 -0000 [thread overview]
Message-ID: <20180622104652.30805.82815@emeril.freedesktop.org> (raw)
In-Reply-To: <20180622104134.6823-1-mahesh1.kumar@intel.com>
== Series Details ==
Series: Improve crc-core driver interface
URL : https://patchwork.freedesktop.org/series/45246/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
029f1bb122df drm: crc: Introduce verify_crc_source callback
5ec7aa87b40a drm: crc: Introduce pre_crc_read function
480f7d04332c drm: crc: Introduce get_crc_sources callback
d4423129d7d1 drm/rockchip/crc: Implement verify_crc_source callback
-:21: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#21: FILE: drivers/gpu/drm/rockchip/rockchip_drm_vop.c:1143:
+static int vop_crtc_verify_crc_source(struct drm_crtc *crtc,
+ const char *source_name, size_t *values_cnt)
-:39: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#39: FILE: drivers/gpu/drm/rockchip/rockchip_drm_vop.c:1161:
+static int vop_crtc_verify_crc_source(struct drm_crtc *crtc,
+ const char *source_name, size_t *values_cnt)
total: 0 errors, 0 warnings, 2 checks, 37 lines checked
610d591b94d6 drm/amdgpu_dm/crc: Implement verify_crc_source callback
891094e98e2a drm/rcar-du/crc: Implement verify_crc_source callback
-:19: CHECK:LINE_SPACING: Please don't use multiple blank lines
#19: FILE: drivers/gpu/drm/rcar-du/rcar_du_crtc.c:759:
+
-:37: CHECK:BRACES: Blank lines aren't necessary after an open brace '{'
#37: FILE: drivers/gpu/drm/rcar-du/rcar_du_crtc.c:777:
+ } else if (strstarts(source_name, "plane")) {
+
total: 0 errors, 0 warnings, 2 checks, 54 lines checked
8bba28049862 drm/i915/crc: implement verify_crc_source callback
-:137: CHECK:LINE_SPACING: Please don't use multiple blank lines
#137: FILE: drivers/gpu/drm/i915/intel_pipe_crc.c:1004:
+
+
-:150: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#150: FILE: drivers/gpu/drm/i915/intel_pipe_crc.c:1017:
+ if (source == INTEL_PIPE_CRC_SOURCE_AUTO ||
+ intel_is_valid_crc_source(dev_priv, source) == 0) {
total: 0 errors, 0 warnings, 2 checks, 135 lines checked
042fb1777a2a drm/i915/crc: implement get_crc_sources callback
4820bcc2bfff drm/crc: Cleanup crtc_crc_open function
3493f69dc14c Revert "drm: crc: Wait for a frame before returning from open()"
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-06-22 10:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 10:41 [PATCH 00/10] Improve crc-core driver interface Mahesh Kumar
2018-06-22 10:41 ` [PATCH 01/10] drm: crc: Introduce verify_crc_source callback Mahesh Kumar
2018-06-25 15:38 ` Daniel Vetter
2018-06-22 10:41 ` [PATCH 02/10] drm: crc: Introduce pre_crc_read function Mahesh Kumar
2018-06-22 10:41 ` [PATCH 03/10] drm: crc: Introduce get_crc_sources callback Mahesh Kumar
2018-06-22 10:41 ` [PATCH 04/10] drm/rockchip/crc: Implement verify_crc_source callback Mahesh Kumar
2018-06-22 10:41 ` [PATCH 05/10] drm/amdgpu_dm/crc: " Mahesh Kumar
2018-06-22 10:41 ` [PATCH 06/10] drm/rcar-du/crc: " Mahesh Kumar
2018-06-22 10:41 ` [PATCH 07/10] drm/i915/crc: implement " Mahesh Kumar
2018-06-22 10:41 ` [PATCH 08/10] drm/i915/crc: implement get_crc_sources callback Mahesh Kumar
2018-06-22 10:41 ` [PATCH 09/10] drm/crc: Cleanup crtc_crc_open function Mahesh Kumar
2018-06-22 10:41 ` [PATCH 10/10] Revert "drm: crc: Wait for a frame before returning from open()" Mahesh Kumar
2018-06-22 12:30 ` Maarten Lankhorst
2018-06-22 15:03 ` Tomeu Vizoso
2018-06-22 10:46 ` Patchwork [this message]
2018-06-22 11:01 ` ✗ Fi.CI.BAT: failure for Improve crc-core driver interface 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=20180622104652.30805.82815@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mahesh1.kumar@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