From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Ville Syrjala" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Init DDI ports in VBT order (rev4)
Date: Tue, 20 Jun 2023 21:30:13 -0000 [thread overview]
Message-ID: <168729661345.10439.7915800982503789792@emeril.freedesktop.org> (raw)
In-Reply-To: <20230620173242.26923-1-ville.syrjala@linux.intel.com>
== Series Details ==
Series: drm/i915: Init DDI ports in VBT order (rev4)
URL : https://patchwork.freedesktop.org/series/114200/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
next prev parent reply other threads:[~2023-06-20 21:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 17:32 [Intel-gfx] [PATCH v2 0/5] drm/i915: Init DDI ports in VBT order Ville Syrjala
2023-06-20 17:32 ` [Intel-gfx] [PATCH v2 1/5] drm/i915: Initialize dig_port->aux_ch to NONE to be sure Ville Syrjala
2023-06-21 7:44 ` Jani Nikula
2023-06-20 17:32 ` [Intel-gfx] [PATCH v2 2/5] drm/i915: Only populate aux_ch is really needed Ville Syrjala
2023-06-21 7:46 ` Jani Nikula
2023-06-21 7:47 ` Jani Nikula
2023-06-20 17:32 ` [Intel-gfx] [PATCH v2 3/5] drm/i915: Remove DDC pin sanitation Ville Syrjala
2023-06-21 7:56 ` Jani Nikula
2023-06-29 14:04 ` Ville Syrjälä
2023-06-20 17:32 ` [Intel-gfx] [PATCH v2 4/5] drm/i915: Remove AUX CH sanitation Ville Syrjala
2023-06-21 8:00 ` Jani Nikula
2023-06-21 13:13 ` Ville Syrjälä
2023-06-20 17:32 ` [Intel-gfx] [PATCH v2 5/5] drm/i915: Try to initialize DDI/ICL+ DSI ports for every VBT child device Ville Syrjala
2023-06-26 13:06 ` Jani Nikula
2023-06-29 14:13 ` Ville Syrjälä
2023-06-20 21:30 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Init DDI ports in VBT order (rev4) Patchwork
2023-06-20 21:30 ` Patchwork [this message]
2023-06-20 21:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-21 5:42 ` [Intel-gfx] ✓ 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=168729661345.10439.7915800982503789792@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox