From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Manna, Animesh" <animesh.manna@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/pps: Add get_pps_idx() hook as part of pps_get_register() cleanup
Date: Mon, 10 Oct 2022 16:37:30 -0000 [thread overview]
Message-ID: <166541985019.29670.7914540399893352356@emeril.freedesktop.org> (raw)
In-Reply-To: <20221010155427.15735-1-animesh.manna@intel.com>
== Series Details ==
Series: series starting with [1/2] drm/i915/pps: Add get_pps_idx() hook as part of pps_get_register() cleanup
URL : https://patchwork.freedesktop.org/series/109547/
State : warning
== Summary ==
Error: dim checkpatch failed
25167c11f19e drm/i915/pps: Add get_pps_idx() hook as part of pps_get_register() cleanup
f59d1e59c801 drm/i915/pps: Enable 2nd pps for dual EDP scenario
-:11: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#11:
for a specific panel. Currently dual PPS support is broken. This patch fixes
total: 0 errors, 1 warnings, 0 checks, 99 lines checked
next prev parent reply other threads:[~2022-10-10 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 15:54 [Intel-gfx] [PATCH 1/2] drm/i915/pps: Add get_pps_idx() hook as part of pps_get_register() cleanup Animesh Manna
2022-10-10 15:54 ` [Intel-gfx] [PATCH 2/2] drm/i915/pps: Enable 2nd pps for dual EDP scenario Animesh Manna
2022-10-17 13:08 ` Jani Nikula
2022-10-18 8:50 ` Manna, Animesh
2022-10-10 16:37 ` Patchwork [this message]
2022-10-10 16:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/pps: Add get_pps_idx() hook as part of pps_get_register() cleanup Patchwork
2022-10-10 21:56 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-10-17 12:20 ` [Intel-gfx] [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=166541985019.29670.7914540399893352356@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=animesh.manna@intel.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.