From: Patchwork <patchwork@emeril.freedesktop.org>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for Modular FIA
Date: Thu, 04 Jul 2019 01:04:03 -0000 [thread overview]
Message-ID: <20190704010403.7777.62335@emeril.freedesktop.org> (raw)
In-Reply-To: <20190704000649.20661-1-lucas.demarchi@intel.com>
== Series Details ==
Series: Modular FIA
URL : https://patchwork.freedesktop.org/series/63175/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: make new intel_tc.c use uncore accessors
Okay!
Commit: drm/i915: fix include order in intel_tc.*
Okay!
Commit: drm/i915: move intel_ddi_set_fia_lane_count to intel_tc.c
Okay!
Commit: drm/i915: Add modular FIA
+drivers/gpu/drm/i915/display/intel_tc.c:41:14: warning: symbol 'tc_port_to_fia' was not declared. Should it be static?
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-04 1:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 0:06 [PATCH 0/4] Modular FIA Lucas De Marchi
2019-07-04 0:06 ` [PATCH 1/4] drm/i915: make new intel_tc.c use uncore accessors Lucas De Marchi
2019-07-04 0:06 ` [PATCH 2/4] drm/i915: fix include order in intel_tc.* Lucas De Marchi
2019-07-04 13:56 ` Imre Deak
2019-07-08 15:13 ` Lucas De Marchi
2019-08-05 9:16 ` Jani Nikula
2019-07-04 17:21 ` Michal Wajdeczko
2019-07-04 17:43 ` Imre Deak
2019-07-04 17:56 ` Michal Wajdeczko
2019-07-04 18:53 ` Imre Deak
2019-07-08 15:16 ` Lucas De Marchi
2019-07-04 0:06 ` [PATCH 3/4] drm/i915: move intel_ddi_set_fia_lane_count to intel_tc.c Lucas De Marchi
2019-07-04 14:03 ` Imre Deak
2019-07-04 0:06 ` [PATCH 4/4] drm/i915: Add modular FIA Lucas De Marchi
2019-07-04 1:04 ` Patchwork [this message]
2019-07-04 1:39 ` ✓ Fi.CI.BAT: success for Modular FIA Patchwork
2019-07-05 4:55 ` ✓ 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=20190704010403.7777.62335@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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