All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jani Nikula" <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: refactor intel_display.c + a bit more
Date: Thu, 04 Feb 2021 22:47:19 -0000	[thread overview]
Message-ID: <161247883936.4504.13903183884997634840@emeril.freedesktop.org> (raw)
In-Reply-To: <cover.1612467466.git.jani.nikula@intel.com>

== Series Details ==

Series: drm/i915: refactor intel_display.c + a bit more
URL   : https://patchwork.freedesktop.org/series/86723/
State : warning

== Summary ==

$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c:742:28: warning: symbol 'bdw_get_buf_trans_edp' was not declared. Should it be static?
+drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c:756:28: warning: symbol 'skl_get_buf_trans_dp' was not declared. Should it be static?
+drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c:773:28: warning: symbol 'kbl_get_buf_trans_dp' was not declared. Should it be static?
+drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c:794:28: warning: symbol 'skl_get_buf_trans_edp' was not declared. Should it be static?
+drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c:826:28: warning: symbol 'skl_get_buf_trans_hdmi' was not declared. Should it be static?
+drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c:841:5: warning: symbol 'skl_buf_trans_num_entries' was not declared. Should it be static?
+drivers/gpu/drm/i915/intel_wakeref.c:137:19: warning: context imbalance in 'wakeref_auto_timeout' - unexpected unlock


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2021-02-04 22:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 19:43 [Intel-gfx] [PATCH v11 00/10] drm/i915: refactor intel_display.c + a bit more Jani Nikula
2021-02-04 19:43 ` [Intel-gfx] [PATCH v11 01/10] drm/i915: refactor ddi translations into a separate file (v2) Jani Nikula
2021-02-05 13:48   ` Jani Nikula
2021-02-04 19:43 ` [Intel-gfx] [PATCH v11 02/10] drm/i915: migrate hsw fdi code to new file Jani Nikula
2021-02-05 13:52   ` Jani Nikula
2021-02-04 19:43 ` [Intel-gfx] [PATCH v11 03/10] drm/i915: migrate skl planes code new file (v5) Jani Nikula
2021-02-04 20:28   ` Ville Syrjälä
2021-02-04 20:35     ` Jani Nikula
2021-02-04 19:43 ` [Intel-gfx] [PATCH v11 04/10] drm/i915: move pipe update code into crtc. (v2) Jani Nikula
2021-02-04 19:43 ` [Intel-gfx] [PATCH v11 05/10] drm/i915: split fb scalable checks into g4x and skl versions Jani Nikula
2021-02-04 19:43 ` [Intel-gfx] [PATCH v11 06/10] drm/i915: move is_ccs_modifier to an inline Jani Nikula
2021-02-04 19:43 ` [Intel-gfx] [PATCH v11 07/10] drm/i915: migrate pll enable/disable code to intel_dpll.[ch] Jani Nikula
2021-02-04 19:43 ` [Intel-gfx] [PATCH v11 08/10] drm/i915: migrate i9xx plane get config Jani Nikula
2021-02-04 19:43 ` [Intel-gfx] [PATCH v11 09/10] drm/i915: refactor skylake scaler code into new file Jani Nikula
2021-02-04 20:35   ` Ville Syrjälä
2021-02-04 19:43 ` [Intel-gfx] [PATCH v11 10/10] drm/i915: move ddi pll state get to dpll mgr Jani Nikula
2021-02-04 22:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: refactor intel_display.c + a bit more Patchwork
2021-02-04 22:47 ` Patchwork [this message]
2021-02-04 23:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-02-05  6:46 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=161247883936.4504.13903183884997634840@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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.