From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/wm: remove stale and unused ilk_wm_max_level() declaration
Date: Wed, 19 Apr 2023 15:33:58 +0300 [thread overview]
Message-ID: <ZD/ftpzg9AbB3GMn@intel.com> (raw)
In-Reply-To: <20230419115449.422214-1-jani.nikula@intel.com>
On Wed, Apr 19, 2023 at 02:54:49PM +0300, Jani Nikula wrote:
> The declaration was removed earlier, but got accidentally resurrected in
> i915xx_wm.[ch] refactoring. Remove harder.
i9xx_wm
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/i9xx_wm.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/i9xx_wm.h b/drivers/gpu/drm/i915/display/i9xx_wm.h
> index a7875cbcd05a..b87ae369685a 100644
> --- a/drivers/gpu/drm/i915/display/i9xx_wm.h
> +++ b/drivers/gpu/drm/i915/display/i9xx_wm.h
> @@ -12,7 +12,6 @@ struct drm_i915_private;
> struct intel_crtc_state;
> struct intel_plane_state;
>
> -int ilk_wm_max_level(const struct drm_i915_private *i915);
> bool ilk_disable_lp_wm(struct drm_i915_private *i915);
> void ilk_wm_sanitize(struct drm_i915_private *i915);
> bool intel_set_memory_cxsr(struct drm_i915_private *i915, bool enable);
> --
> 2.39.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-04-19 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 11:54 [Intel-gfx] [PATCH] drm/i915/wm: remove stale and unused ilk_wm_max_level() declaration Jani Nikula
2023-04-19 12:33 ` Ville Syrjälä [this message]
2023-04-20 10:58 ` Jani Nikula
2023-04-19 18:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-04-19 21:58 ` [Intel-gfx] ✓ 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=ZD/ftpzg9AbB3GMn@intel.com \
--to=ville.syrjala@linux.intel.com \
--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.