From: kernel test robot <lkp@intel.com> To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>, intel-gfx@lists.freedesktop.org Cc: kbuild-all@lists.01.org Subject: [Intel-gfx] [RFC PATCH] drm/i915: dg2_async_flip_optimization() can be static Date: Wed, 8 Dec 2021 10:30:26 +0800 [thread overview] Message-ID: <20211208023026.GA134840@162bc3755f23> (raw) In-Reply-To: <20211207110721.30409-3-stanislav.lisovskiy@intel.com> drivers/gpu/drm/i915/intel_pm.c:5500:6: warning: symbol 'dg2_async_flip_optimization' was not declared. Should it be static? Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: kernel test robot <lkp@intel.com> --- intel_pm.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c index 658a5dbb8fa4f..1d9880b9aa7dd 100644 --- a/drivers/gpu/drm/i915/intel_pm.c +++ b/drivers/gpu/drm/i915/intel_pm.c @@ -5497,9 +5497,9 @@ static int skl_wm_max_lines(struct drm_i915_private *dev_priv) return 31; } -bool dg2_async_flip_optimization(struct drm_i915_private *i915, - const struct intel_crtc_state *crtc_state, - const struct intel_plane *plane) +static bool dg2_async_flip_optimization(struct drm_i915_private *i915, + const struct intel_crtc_state *crtc_state, + const struct intel_plane *plane) { return DISPLAY_VER(i915) >= 13 && crtc_state->uapi.async_flip &&
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com> To: kbuild-all@lists.01.org Subject: [RFC PATCH] drm/i915: dg2_async_flip_optimization() can be static Date: Wed, 08 Dec 2021 10:30:26 +0800 [thread overview] Message-ID: <20211208023026.GA134840@162bc3755f23> (raw) In-Reply-To: <20211207110721.30409-3-stanislav.lisovskiy@intel.com> [-- Attachment #1: Type: text/plain, Size: 1018 bytes --] drivers/gpu/drm/i915/intel_pm.c:5500:6: warning: symbol 'dg2_async_flip_optimization' was not declared. Should it be static? Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: kernel test robot <lkp@intel.com> --- intel_pm.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c index 658a5dbb8fa4f..1d9880b9aa7dd 100644 --- a/drivers/gpu/drm/i915/intel_pm.c +++ b/drivers/gpu/drm/i915/intel_pm.c @@ -5497,9 +5497,9 @@ static int skl_wm_max_lines(struct drm_i915_private *dev_priv) return 31; } -bool dg2_async_flip_optimization(struct drm_i915_private *i915, - const struct intel_crtc_state *crtc_state, - const struct intel_plane *plane) +static bool dg2_async_flip_optimization(struct drm_i915_private *i915, + const struct intel_crtc_state *crtc_state, + const struct intel_plane *plane) { return DISPLAY_VER(i915) >= 13 && crtc_state->uapi.async_flip &&
next prev parent reply other threads:[~2021-12-08 2:31 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-07 11:07 [Intel-gfx] [PATCH 1/4] drm/i915: Pass plane to watermark calculation functions Stanislav Lisovskiy 2021-12-07 11:07 ` [Intel-gfx] [PATCH 2/4] drm/i915: Introduce do_async_flip flag to intel_plane_state Stanislav Lisovskiy 2021-12-07 11:07 ` [Intel-gfx] [PATCH 3/4] drm/i915: Use wm0 only during async flips for DG2 Stanislav Lisovskiy 2021-12-07 17:52 ` kernel test robot 2021-12-07 17:52 ` kernel test robot 2021-12-07 18:12 ` kernel test robot 2021-12-07 18:12 ` kernel test robot 2021-12-07 20:25 ` kernel test robot 2021-12-07 20:25 ` kernel test robot 2021-12-08 2:30 ` kernel test robot [this message] 2021-12-08 2:30 ` [RFC PATCH] drm/i915: dg2_async_flip_optimization() can be static kernel test robot 2021-12-08 2:34 ` [Intel-gfx] [PATCH 3/4] drm/i915: Use wm0 only during async flips for DG2 kernel test robot 2021-12-08 2:34 ` kernel test robot 2021-12-07 11:07 ` [Intel-gfx] [PATCH 4/4] drm/i915: Don't allocate extra ddb during async flip " Stanislav Lisovskiy 2021-12-07 11:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915: Pass plane to watermark calculation functions Patchwork 2021-12-07 11:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork 2021-12-07 12:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2021-12-07 14:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork 2021-12-09 11:03 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915: Pass plane to watermark calculation functions (rev2) Patchwork 2021-12-09 11:04 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork 2021-12-09 11:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2021-12-09 16:31 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork 2021-12-13 16:08 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915: Pass plane to watermark calculation functions (rev3) Patchwork 2021-12-13 16:09 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork 2021-12-13 16:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2021-12-13 23:24 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork 2022-01-11 16:53 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915: Pass plane to watermark calculation functions (rev4) Patchwork 2022-01-11 16:54 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork 2022-01-11 17:10 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork 2022-01-12 7:16 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915: Pass plane to watermark calculation functions (rev5) Patchwork 2022-01-12 7:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork 2022-01-12 7:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2022-01-12 11:01 ` [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=20211208023026.GA134840@162bc3755f23 \ --to=lkp@intel.com \ --cc=intel-gfx@lists.freedesktop.org \ --cc=kbuild-all@lists.01.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.