From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915: Consult VBT "LVDS config" bits to determine whether internal LVDS is present
Date: Fri, 04 May 2018 14:33:27 -0000 [thread overview]
Message-ID: <20180504143327.23926.75592@emeril.freedesktop.org> (raw)
In-Reply-To: <20180504141349.5878-1-ville.syrjala@linux.intel.com>
== Series Details ==
Series: series starting with [1/2] drm/i915: Consult VBT "LVDS config" bits to determine whether internal LVDS is present
URL : https://patchwork.freedesktop.org/series/42690/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
55f6fb40253e drm/i915: Consult VBT "LVDS config" bits to determine whether internal LVDS is present
-:32: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#32:
References: https://lists.freedesktop.org/archives/intel-gfx/2018-March/158408.html
total: 0 errors, 1 warnings, 0 checks, 73 lines checked
1b01d8a4324f drm/i915: Eliminate the unused dev_priv->vbt.lvds_vbt
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-05-04 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 14:13 [PATCH 1/2] drm/i915: Consult VBT "LVDS config" bits to determine whether internal LVDS is present Ville Syrjala
2018-05-04 14:13 ` [PATCH 2/2] drm/i915: Eliminate the unused dev_priv->vbt.lvds_vbt Ville Syrjala
2018-05-04 20:14 ` Rodrigo Vivi
2018-05-04 14:33 ` Patchwork [this message]
2018-05-04 14:34 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/i915: Consult VBT "LVDS config" bits to determine whether internal LVDS is present Patchwork
2018-05-04 14:49 ` ✓ Fi.CI.BAT: success " Patchwork
2018-05-04 16:22 ` ✓ Fi.CI.IGT: " Patchwork
2018-05-08 9:33 ` [PATCH 1/2] " Jani Nikula
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=20180504143327.23926.75592@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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.