From: Patchwork <patchwork@emeril.freedesktop.org> To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com> Cc: intel-gfx@lists.freedesktop.org Subject: ✗ Fi.CI.SPARSE: warning for drm/i915: Enable second dbuf slice for ICL and TGL Date: Thu, 07 Nov 2019 17:41:44 -0000 [thread overview] Message-ID: <157314850498.21753.9948031232880261212@emeril.freedesktop.org> (raw) In-Reply-To: <20191107131020.12869-1-stanislav.lisovskiy@intel.com> == Series Details == Series: drm/i915: Enable second dbuf slice for ICL and TGL URL : https://patchwork.freedesktop.org/series/69124/ State : warning == Summary == $ dim sparse origin/drm-tip Sparse version: v0.6.0 Commit: drm/i915: Enable second dbuf slice for ICL and TGL +drivers/gpu/drm/i915/intel_pm.c:4253:1: warning: symbol 'skl_pipe_downscale_amount' was not declared. Should it be static? +drivers/gpu/drm/i915/intel_pm.c:4274:1: warning: symbol 'icl_get_pipe_ratio' was not declared. Should it be static? +drivers/gpu/drm/i915/intel_pm.c:4371:30: warning: symbol 'icl_allowed_dbufs' was not declared. Should it be static? +drivers/gpu/drm/i915/intel_pm.c:4395:30: warning: symbol 'tgl_allowed_dbufs' was not declared. Should it be static? +drivers/gpu/drm/i915/intel_pm.c:4465:5: warning: symbol 'i915_get_allowed_dbuf_mask' was not declared. Should it be static? _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Patchwork <patchwork@emeril.freedesktop.org> To: "Stanislav Lisovskiy" <stanislav.lisovskiy@intel.com> Cc: intel-gfx@lists.freedesktop.org Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Enable second dbuf slice for ICL and TGL Date: Thu, 07 Nov 2019 17:41:44 -0000 [thread overview] Message-ID: <157314850498.21753.9948031232880261212@emeril.freedesktop.org> (raw) Message-ID: <20191107174144.sL2152F5eNoINQqjoaq2QF5EpSeH_iIbHe_821wso7E@z> (raw) In-Reply-To: <20191107131020.12869-1-stanislav.lisovskiy@intel.com> == Series Details == Series: drm/i915: Enable second dbuf slice for ICL and TGL URL : https://patchwork.freedesktop.org/series/69124/ State : warning == Summary == $ dim sparse origin/drm-tip Sparse version: v0.6.0 Commit: drm/i915: Enable second dbuf slice for ICL and TGL +drivers/gpu/drm/i915/intel_pm.c:4253:1: warning: symbol 'skl_pipe_downscale_amount' was not declared. Should it be static? +drivers/gpu/drm/i915/intel_pm.c:4274:1: warning: symbol 'icl_get_pipe_ratio' was not declared. Should it be static? +drivers/gpu/drm/i915/intel_pm.c:4371:30: warning: symbol 'icl_allowed_dbufs' was not declared. Should it be static? +drivers/gpu/drm/i915/intel_pm.c:4395:30: warning: symbol 'tgl_allowed_dbufs' was not declared. Should it be static? +drivers/gpu/drm/i915/intel_pm.c:4465:5: warning: symbol 'i915_get_allowed_dbuf_mask' 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-11-07 17:41 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-07 13:10 [PATCH v4] drm/i915: Enable second dbuf slice for ICL and TGL Stanislav Lisovskiy 2019-11-07 13:10 ` [Intel-gfx] " Stanislav Lisovskiy 2019-11-07 17:40 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2019-11-07 17:40 ` [Intel-gfx] " Patchwork 2019-11-07 17:41 ` Patchwork [this message] 2019-11-07 17:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork 2019-11-07 18:12 ` ✗ Fi.CI.BAT: failure " Patchwork 2019-11-07 18:12 ` [Intel-gfx] " 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=157314850498.21753.9948031232880261212@emeril.freedesktop.org \ --to=patchwork@emeril.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=stanislav.lisovskiy@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: linkBe 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.