All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Shashank Sharma <shashank.sharma@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for YCBCR 4:2:0/4:4:4 output support for LSPCON (rev8)
Date: Wed, 30 May 2018 11:01:07 -0000	[thread overview]
Message-ID: <20180530110107.31295.37139@emeril.freedesktop.org> (raw)
In-Reply-To: <1527675475-18114-1-git-send-email-shashank.sharma@intel.com>

== Series Details ==

Series: YCBCR 4:2:0/4:4:4 output support for LSPCON (rev8)
URL   : https://patchwork.freedesktop.org/series/36068/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
15891a2047c1 drm/i915: Introduce CRTC output format
22f13096d17e drm/i915: Add CRTC output format YCBCR 4:2:0
67ec2782ab55 drm/i915: Add CRTC output format YCBCR 4:4:4
7cdafd96c1e4 drm/i915: Check LSPCON vendor OUI
e15310784af1 drm/i915: Add AVI infoframe support for LSPCON
42085377b498 drm/i915: Write AVI infoframes for MCA LSPCON
6fcc9ce4c7b3 drm/i915: Write AVI infoframes for Parade LSPCON
cab98d0b19ea drm/i915: Add YCBCR 4:2:0/4:4:4 support for LSPCON
-:65: CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV)
#65: FILE: drivers/gpu/drm/i915/i915_reg.h:8834:
+#define  TRANS_MSA_SAMPLING_444		(2<<1)
                                		  ^

-:66: CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV)
#66: FILE: drivers/gpu/drm/i915/i915_reg.h:8835:
+#define  TRANS_MSA_CLRSP_YCBCR		(2<<3)
                               		  ^

total: 0 errors, 0 warnings, 2 checks, 128 lines checked

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-05-30 11:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 10:17 [REBASE v9 0/8] YCBCR 4:2:0/4:4:4 output support for LSPCON Shashank Sharma
2018-05-30 10:17 ` [REBASE v9 1/8] drm/i915: Introduce CRTC output format Shashank Sharma
2018-05-30 10:17 ` [REBASE v9 2/8] drm/i915: Add CRTC output format YCBCR 4:2:0 Shashank Sharma
2018-05-30 10:17 ` [REBASE v9 3/8] drm/i915: Add CRTC output format YCBCR 4:4:4 Shashank Sharma
2018-05-30 10:17 ` [REBASE v9 4/8] drm/i915: Check LSPCON vendor OUI Shashank Sharma
2018-05-30 10:17 ` [REBASE v9 5/8] drm/i915: Add AVI infoframe support for LSPCON Shashank Sharma
2018-05-30 10:17 ` [REBASE v9 6/8] drm/i915: Write AVI infoframes for MCA LSPCON Shashank Sharma
2018-06-05  9:30   ` [PATCH v9 5/8] drm/i915: Add AVI infoframe support for LSPCON Shashank Sharma
2018-06-05  9:32   ` [PATCH v9 6/8] drm/i915: Write AVI infoframes for MCA LSPCON Shashank Sharma
2018-05-30 10:17 ` [REBASE v9 7/8] drm/i915: Write AVI infoframes for Parade LSPCON Shashank Sharma
2018-05-30 10:17 ` [REBASE v9 8/8] drm/i915: Add YCBCR 4:2:0/4:4:4 support for LSPCON Shashank Sharma
2018-05-30 11:01 ` Patchwork [this message]
2018-05-30 11:22 ` ✗ Fi.CI.BAT: failure for YCBCR 4:2:0/4:4:4 output support for LSPCON (rev8) Patchwork
2018-06-05 11:02 ` ✗ Fi.CI.CHECKPATCH: warning for YCBCR 4:2:0/4:4:4 output support for LSPCON (rev10) Patchwork
2018-06-05 11:18 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-06-05 13:11 ` ✗ 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=20180530110107.31295.37139@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=shashank.sharma@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.