From: Jani Nikula <jani.nikula@intel.com>
To: Arun R Murthy <arun.r.murthy@intel.com>,
intel-xe@lists.freedesktop.org, uma.shankar@intel.com
Cc: Arun R Murthy <arun.r.murthy@intel.com>
Subject: Re: [Intel-xe] [PATCH 1/2] Revert "FIXME: drm/i915: xe doesn't have fastboot module parameter"
Date: Thu, 12 Oct 2023 12:56:45 +0300 [thread overview]
Message-ID: <877cns2mg2.fsf@intel.com> (raw)
In-Reply-To: <20231012093446.1332238-1-arun.r.murthy@intel.com>
On Thu, 12 Oct 2023, Arun R Murthy <arun.r.murthy@intel.com> wrote:
> The modparam fastboot is removed from i915.
>
> This reverts commit 3c73fdaf8f58b55b0e292fec0929b6502c2b3a3e.
Acked-by: Jani Nikula <jani.nikula@intel.com>
on both
> ---
> drivers/gpu/drm/i915/display/intel_display.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index 4b73db93d23d..e876fa6db285 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -4988,7 +4988,6 @@ pipe_config_mismatch(bool fastset, const struct intel_crtc *crtc,
>
> static bool fastboot_enabled(struct drm_i915_private *dev_priv)
> {
> -#ifdef I915
> if (dev_priv->params.fastboot != -1)
> return dev_priv->params.fastboot;
>
> @@ -5002,9 +5001,6 @@ static bool fastboot_enabled(struct drm_i915_private *dev_priv)
>
> /* Disabled by default on all others */
> return false;
> -#else
> - return true;
> -#endif
> }
>
> bool
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-10-12 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 9:34 [Intel-xe] [PATCH 1/2] Revert "FIXME: drm/i915: xe doesn't have fastboot module parameter" Arun R Murthy
2023-10-12 9:34 ` [Intel-xe] [PATCH 2/2] drm/i915: Remove the module parameter 'fastboot' Arun R Murthy
2023-10-12 9:46 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/2] Revert "FIXME: drm/i915: xe doesn't have fastboot module parameter" Patchwork
2023-10-12 9:46 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-12 9:48 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-12 9:55 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-12 9:55 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-12 9:56 ` Jani Nikula [this message]
2023-10-13 21:11 ` [Intel-xe] [PATCH 1/2] " Rodrigo Vivi
2023-10-12 9:56 ` [Intel-xe] ✗ CI.checksparse: warning for series starting with [1/2] " Patchwork
2023-10-12 10:21 ` [Intel-xe] ✓ CI.BAT: success " 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=877cns2mg2.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=uma.shankar@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.