From: Patchwork <patchwork@emeril.freedesktop.org>
To: Vandita Kulkarni <vandita.kulkarni@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [v3,1/4] drm/i915: Fix the pipe state timing mismatch warnings
Date: Thu, 02 May 2019 07:18:02 -0000 [thread overview]
Message-ID: <20190502071802.26884.79429@emeril.freedesktop.org> (raw)
In-Reply-To: <1556778847-7796-1-git-send-email-vandita.kulkarni@intel.com>
== Series Details ==
Series: series starting with [v3,1/4] drm/i915: Fix the pipe state timing mismatch warnings
URL : https://patchwork.freedesktop.org/series/60186/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
4f4166d5345c drm/i915: Fix the pipe state timing mismatch warnings
-:48: CHECK:BRACES: Blank lines aren't necessary before a close brace '}'
#48: FILE: drivers/gpu/drm/i915/icl_dsi.c:1223:
+
+}
total: 0 errors, 0 warnings, 1 checks, 41 lines checked
acb46e6ef365 drm/i915: Refactor bdw_get_pipemisc_bpp
387ba833429c drm/i915: Fix pipe config mismatch for bpp, output format
2538e2d41f5e drm/i915: Fix pixel clock and crtc clock config mismatch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-02 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 6:34 [v3 1/4] drm/i915: Fix the pipe state timing mismatch warnings Vandita Kulkarni
2019-05-02 6:34 ` [v3 2/4] drm/i915: Refactor bdw_get_pipemisc_bpp Vandita Kulkarni
2019-05-02 6:34 ` [v3 3/4] drm/i915: Fix pipe config mismatch for bpp, output format Vandita Kulkarni
2019-05-02 6:34 ` [v3 4/4] drm/i915: Fix pixel clock and crtc clock config mismatch Vandita Kulkarni
2019-05-02 7:18 ` Patchwork [this message]
2019-05-02 7:35 ` ✓ Fi.CI.BAT: success for series starting with [v3,1/4] drm/i915: Fix the pipe state timing mismatch warnings Patchwork
2019-05-02 13:21 ` ✓ 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=20190502071802.26884.79429@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vandita.kulkarni@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