From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for drm/i915: Some plane init cleanups
Date: Fri, 05 Oct 2018 13:51:58 -0000 [thread overview]
Message-ID: <20181005135158.1893.20857@emeril.freedesktop.org> (raw)
In-Reply-To: <20181005125817.22576-1-ville.syrjala@linux.intel.com>
== Series Details ==
Series: drm/i915: Some plane init cleanups
URL : https://patchwork.freedesktop.org/series/50615/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Constify all plane_funcs structs
Okay!
Commit: drm/i915: Populate possible_crtcs for primary/cursor planes
Okay!
Commit: drm/i915: Don't populate plane->i9xx_plane for sprites
Okay!
Commit: drm/i915: Allow horizontal mirroring for cnl+ "sprite" planes
Okay!
Commit: drm/i915: Disallow plane scaling with specific pixel formats
Okay!
Commit: drm/i915: Add missing pixel formats for skl+ "sprites"
Okay!
Commit: drm/i915: Move plane_state->scaler_id initialization into intel_create_plane_state()
Okay!
Commit: drm/i915: Introduce intel_plane_alloc()
Okay!
Commit: drm/i915: Extract skl_universal_plane_init()
+drivers/gpu/drm/i915/intel_sprite.c:364:1: warning: symbol 'skl_update_plane' was not declared. Should it be static?
Commit: drm/i915: s/intel_plane/plane/ in sprite init
Okay!
Commit: drm/i915: Rename variables in intel_primary_plane_create()
Okay!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-05 13:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 12:58 [PATCH v4 00/11] drm/i915: Some plane init cleanups Ville Syrjala
2018-10-05 12:58 ` [PATCH v4 01/11] drm/i915: Constify all plane_funcs structs Ville Syrjala
2018-10-05 12:58 ` [PATCH v4 02/11] drm/i915: Populate possible_crtcs for primary/cursor planes Ville Syrjala
2018-10-05 12:58 ` [PATCH v4 03/11] drm/i915: Don't populate plane->i9xx_plane for sprites Ville Syrjala
2018-10-05 12:58 ` [PATCH v4 04/11] drm/i915: Allow horizontal mirroring for cnl+ "sprite" planes Ville Syrjala
2018-10-05 12:58 ` [PATCH v4 05/11] drm/i915: Disallow plane scaling with specific pixel formats Ville Syrjala
2018-10-05 12:58 ` [PATCH v4 06/11] drm/i915: Add missing pixel formats for skl+ "sprites" Ville Syrjala
2018-10-05 12:58 ` [PATCH v4 07/11] drm/i915: Move plane_state->scaler_id initialization into intel_create_plane_state() Ville Syrjala
2018-10-05 12:58 ` [PATCH v4 08/11] drm/i915: Introduce intel_plane_alloc() Ville Syrjala
2018-10-05 12:58 ` [PATCH v4 09/11] drm/i915: Extract skl_universal_plane_init() Ville Syrjala
2018-10-10 8:13 ` Jani Nikula
2018-10-10 10:18 ` Ville Syrjälä
2018-10-05 12:58 ` [PATCH v4 10/11] drm/i915: s/intel_plane/plane/ in sprite init Ville Syrjala
2018-10-05 12:58 ` [PATCH v4 11/11] drm/i915: Rename variables in intel_primary_plane_create() Ville Syrjala
2018-10-05 13:48 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Some plane init cleanups Patchwork
2018-10-05 13:51 ` Patchwork [this message]
2018-10-05 14:08 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-05 20:40 ` ✓ 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=20181005135158.1893.20857@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.