From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jerry (Fangzhi) Zuo" <Jerry.Zuo@amd.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: Add support for DP 1.4 Compliance edid corruption test (rev3)
Date: Mon, 09 Dec 2019 21:10:26 -0000 [thread overview]
Message-ID: <157592582628.14784.5442440409903140416@emeril.freedesktop.org> (raw)
In-Reply-To: <20191209200442.2625-1-Jerry.Zuo@amd.com>
== Series Details ==
Series: drm: Add support for DP 1.4 Compliance edid corruption test (rev3)
URL : https://patchwork.freedesktop.org/series/70530/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
96a36e9a97da drm: Add support for DP 1.4 Compliance edid corruption test
-:47: ERROR:CODE_INDENT: code indent should use tabs where possible
#47: FILE: drivers/gpu/drm/drm_dp_helper.c:362:
+ u8 real_edid_checksum)$
-:47: WARNING:LEADING_SPACE: please, no spaces at the start of a line
#47: FILE: drivers/gpu/drm/drm_dp_helper.c:362:
+ u8 real_edid_checksum)$
total: 1 errors, 1 warnings, 0 checks, 111 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:[~2019-12-09 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 20:04 [PATCH V4] drm: Add support for DP 1.4 Compliance edid corruption test Jerry (Fangzhi) Zuo
2019-12-09 20:04 ` Jerry (Fangzhi) Zuo
2019-12-09 20:04 ` [Intel-gfx] " Jerry (Fangzhi) Zuo
2019-12-09 21:10 ` Patchwork [this message]
2019-12-09 21:40 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm: Add support for DP 1.4 Compliance edid corruption test (rev3) Patchwork
2019-12-20 19:40 ` Zuo, Jerry
2019-12-20 19:40 ` Zuo, Jerry
2019-12-20 19:52 ` [Intel-gfx] " Harry Wentland
2019-12-20 19:52 ` Harry Wentland
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=157592582628.14784.5442440409903140416@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=Jerry.Zuo@amd.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.