All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Kai-Heng Feng" <kai.heng.feng@canonical.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/lspcon: Limits to 8 bpc for RGB/YCbCr444
Date: Wed, 26 Aug 2020 05:39:31 -0000	[thread overview]
Message-ID: <159842037196.21254.8791932980479196950@emeril.freedesktop.org> (raw)
In-Reply-To: <20200826052143.17607-1-kai.heng.feng@canonical.com>

== Series Details ==

Series: drm/i915/lspcon: Limits to 8 bpc for RGB/YCbCr444
URL   : https://patchwork.freedesktop.org/series/81004/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
a73a2592d427 drm/i915/lspcon: Limits to 8 bpc for RGB/YCbCr444
-:22: CHECK:BRACES: Unbalanced braces around else statement
#22: FILE: drivers/gpu/drm/i915/display/intel_lspcon.c:199:
+	} else

total: 0 errors, 0 warnings, 1 checks, 9 lines checked


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

  reply	other threads:[~2020-08-26  5:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26  5:21 [PATCH] drm/i915/lspcon: Limits to 8 bpc for RGB/YCbCr444 Kai-Heng Feng
2020-08-26  5:21 ` [Intel-gfx] " Kai-Heng Feng
2020-08-26  5:21 ` Kai-Heng Feng
2020-08-26  5:39 ` Patchwork [this message]
2020-08-26  5:57 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2020-08-26 16:24 ` [PATCH] " Ville Syrjälä
2020-08-26 16:24   ` [Intel-gfx] " Ville Syrjälä
2020-08-26 16:24   ` Ville Syrjälä
2020-08-27  5:04   ` Kai Heng Feng
2020-08-27  5:04     ` [Intel-gfx] " Kai Heng Feng
2020-08-27  5:04     ` Kai Heng Feng
2020-08-31 19:48     ` Ville Syrjälä
2020-08-31 19:48       ` [Intel-gfx] " Ville Syrjälä
2020-08-31 19:48       ` Ville Syrjälä
2020-09-02  5:22       ` Kai-Heng Feng
2020-09-02  5:22         ` [Intel-gfx] " Kai-Heng Feng
2020-09-02  5:22         ` Kai-Heng Feng

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=159842037196.21254.8791932980479196950@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kai.heng.feng@canonical.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.