From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Manasi Navare" <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/5] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes
Date: Wed, 28 Oct 2020 05:04:57 -0000 [thread overview]
Message-ID: <160386149794.21342.9395113689985037101@emeril.freedesktop.org> (raw)
In-Reply-To: <20201027221312.16518-1-manasi.d.navare@intel.com>
== Series Details ==
Series: series starting with [v2,1/5] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes
URL : https://patchwork.freedesktop.org/series/83118/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
10e42fe832c7 drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes
2ceb0c198f7f drm/i915: Add hw.pipe_mode to allow bigjoiner pipe/transcoder split
-:10: WARNING:TYPO_SPELLING: 'halfs' may be misspelled - perhaps 'halves'?
#10:
With bigjoiner, there will be 2 pipes driving 2 halfs of 1 transcoder,
-:141: CHECK:MULTIPLE_ASSIGNMENTS: multiple assignments should be avoided
#141: FILE: drivers/gpu/drm/i915/display/intel_display.c:13460:
+ crtc_state->hw.pipe_mode = crtc_state->hw.adjusted_mode = crtc_state->uapi.adjusted_mode;
total: 0 errors, 1 warnings, 1 checks, 357 lines checked
5e1144da1fea drm/i915: Pass intel_atomic_state instead of drm_atomic_state
9b263ae72e3f drm/i915/dp: Prep for bigjoiner atomic check
156703ae1a81 drm/i915/dp: Allow big joiner modes in intel_dp_mode_valid(), v3.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-10-28 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 22:13 [Intel-gfx] [PATCH v2 1/5] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes Manasi Navare
2020-10-27 22:13 ` [Intel-gfx] [PATCH v2 2/5] drm/i915: Add hw.pipe_mode to allow bigjoiner pipe/transcoder split Manasi Navare
2020-10-27 22:13 ` [Intel-gfx] [PATCH v2 3/5] drm/i915: Pass intel_atomic_state instead of drm_atomic_state Manasi Navare
2020-10-27 22:13 ` [Intel-gfx] [PATCH v2 4/5] drm/i915/dp: Prep for bigjoiner atomic check Manasi Navare
2020-10-27 22:13 ` [Intel-gfx] [PATCH v2 5/5] drm/i915/dp: Allow big joiner modes in intel_dp_mode_valid(), v3 Manasi Navare
2020-10-28 5:04 ` Patchwork [this message]
2020-10-28 5:20 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v2,1/5] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes 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=160386149794.21342.9395113689985037101@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=manasi.d.navare@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