All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: "Sasha Levin" <sashal@kernel.org>,
	"Ville Syrjala" <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>,
	stable@vger.kernel.org, Daniel Drake <drake@endlessm.com>,
	Jian-Hong Pan <jian-hong@endlessm.com>
Subject: Re: [PATCH v2 01/14] drm/i915/fbc: Disable fbc by default on all glk+
Date: Fri, 29 Nov 2019 18:34:57 +0000	[thread overview]
Message-ID: <20191129183458.128AD2176D@mail.kernel.org> (raw)
In-Reply-To: <20191127201222.16669-2-ville.syrjala@linux.intel.com>

Hi,

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.3.13, v4.19.86, v4.14.156, v4.9.203, v4.4.203.

v5.3.13: Build OK!
v4.19.86: Failed to apply! Possible dependencies:
    Unable to calculate

v4.14.156: Failed to apply! Possible dependencies:
    Unable to calculate

v4.9.203: Failed to apply! Possible dependencies:
    1d25724b41fa ("drm/i915/fbc: disable framebuffer compression on GeminiLake")
    fd7d6c5c8f3e ("drm/i915: enable FBC on gen9+ too")

v4.4.203: Failed to apply! Possible dependencies:
    0e631adc1aef ("drm/i915: introduce is_active/activate/deactivate to the FBC terminology")
    128d735606d4 ("drm/i915: use a single intel_fbc_work struct")
    1d25724b41fa ("drm/i915/fbc: disable framebuffer compression on GeminiLake")
    30c58d5896e5 ("drm/i915: extract crtc_is_valid() on the FBC code")
    36dbc4d76918 ("drm/i915/fbc: FBC causes display flicker when VT-d is enabled on Skylake")
    45b32a291978 ("drm/i915: use struct intel_crtc *crtc at __intel_fbc_update()")
    571050226c5d ("drm/i915: extract fbc_on_pipe_a_only()")
    754d113304aa ("drm/i915: pass the crtc as an argument to intel_fbc_update()")
    793af070a716 ("drm/i915: remove newline from a no_fbc_reason message")
    80788a0fbbdf ("drm/i915/fbc: sanitize i915.enable_fbc during FBC init")
    913a3a6acae3 ("drm/i915/fbc: don't print no_fbc_reason to dmesg")
    a4dedd5a14a8 ("drm/i915: remove unnecessary check for crtc->primary->fb")
    ab34a7e8b55a ("drm/i915/fbc: replace frequent dev_priv->fbc.x with fbc->x")
    bf6189c6f062 ("drm/i915: change no_fbc_reason from enum to string")
    c68ae339e710 ("drm/i915: don't disable_fbc() if FBC is already disabled")
    e9c5fd26ac38 ("drm/i915: set dev_priv->fbc.crtc before scheduling the enable work")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks,
Sasha
_______________________________________________
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: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
To: Ville Syrjälä <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: , Paulo Zanoni <paulo.r.zanoni@intel.com>,
	stable@vger.kernel.org, Daniel Drake <drake@endlessm.com>,
	Jian-Hong Pan <jian-hong@endlessm.com>
Subject: Re: [Intel-gfx] [PATCH v2 01/14] drm/i915/fbc: Disable fbc by default on all glk+
Date: Fri, 29 Nov 2019 18:34:57 +0000	[thread overview]
Message-ID: <20191129183458.128AD2176D@mail.kernel.org> (raw)
Message-ID: <20191129183457.DWF8qTBqjgyz4t--Y4nic--qfvBbeRajn-Xkd1t_tLU@z> (raw)
In-Reply-To: <20191127201222.16669-2-ville.syrjala@linux.intel.com>

Hi,

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.3.13, v4.19.86, v4.14.156, v4.9.203, v4.4.203.

v5.3.13: Build OK!
v4.19.86: Failed to apply! Possible dependencies:
    Unable to calculate

v4.14.156: Failed to apply! Possible dependencies:
    Unable to calculate

v4.9.203: Failed to apply! Possible dependencies:
    1d25724b41fa ("drm/i915/fbc: disable framebuffer compression on GeminiLake")
    fd7d6c5c8f3e ("drm/i915: enable FBC on gen9+ too")

v4.4.203: Failed to apply! Possible dependencies:
    0e631adc1aef ("drm/i915: introduce is_active/activate/deactivate to the FBC terminology")
    128d735606d4 ("drm/i915: use a single intel_fbc_work struct")
    1d25724b41fa ("drm/i915/fbc: disable framebuffer compression on GeminiLake")
    30c58d5896e5 ("drm/i915: extract crtc_is_valid() on the FBC code")
    36dbc4d76918 ("drm/i915/fbc: FBC causes display flicker when VT-d is enabled on Skylake")
    45b32a291978 ("drm/i915: use struct intel_crtc *crtc at __intel_fbc_update()")
    571050226c5d ("drm/i915: extract fbc_on_pipe_a_only()")
    754d113304aa ("drm/i915: pass the crtc as an argument to intel_fbc_update()")
    793af070a716 ("drm/i915: remove newline from a no_fbc_reason message")
    80788a0fbbdf ("drm/i915/fbc: sanitize i915.enable_fbc during FBC init")
    913a3a6acae3 ("drm/i915/fbc: don't print no_fbc_reason to dmesg")
    a4dedd5a14a8 ("drm/i915: remove unnecessary check for crtc->primary->fb")
    ab34a7e8b55a ("drm/i915/fbc: replace frequent dev_priv->fbc.x with fbc->x")
    bf6189c6f062 ("drm/i915: change no_fbc_reason from enum to string")
    c68ae339e710 ("drm/i915: don't disable_fbc() if FBC is already disabled")
    e9c5fd26ac38 ("drm/i915: set dev_priv->fbc.crtc before scheduling the enable work")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks,
Sasha
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-11-29 18:34 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 20:12 [PATCH v2 00/14] drm/i915/fbc: Fix FBC for glk+ Ville Syrjala
2019-11-27 20:12 ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 01/14] drm/i915/fbc: Disable fbc by default on all glk+ Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-29 18:34   ` Sasha Levin [this message]
2019-11-29 18:34     ` Sasha Levin
2019-11-27 20:12 ` [PATCH v2 02/14] drm/i915/fbc: Nuke bogus single pipe fbc1 restriction Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 03/14] drm/i915: Relocate intel_crtc_active() Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 04/14] drm/i915/fbc: Remove the FBC_RT_BASE setup for ILK/SNB Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 05/14] drm/i915/fbc: Precompute gen9 cfb stride w/a Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 06/14] drm/i915/fbc: Track plane visibility Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 07/14] drm/i915/fbc: Store fence_id direction in fbc cache/params Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 08/14] drm/i915/fbc: Make fence_id optional for i965gm Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 09/14] drm/i915/fbc: s/gen9 && !glk/gen9_bc || bxt/ Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 10/14] drm/i915/fbc: Nuke fbc.enabled Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 11/14] drm/i915/fbc: Start using flip nuke Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 12/14] drm/i915/fbc: Wait for vblank after FBC disable on glk+ Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-28 15:03   ` [PATCH v3 " Ville Syrjala
2019-11-28 15:03     ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 13/14] drm/i915/fbc: Enable fbc by default on glk+ once again Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-27 20:12 ` [PATCH v2 14/14] drm/i915/fbc: Reallocate cfb if we need more of it Ville Syrjala
2019-11-27 20:12   ` [Intel-gfx] " Ville Syrjala
2019-11-28 15:48   ` Maarten Lankhorst
2019-11-28 15:48     ` [Intel-gfx] " Maarten Lankhorst
2019-11-28 15:59     ` Ville Syrjälä
2019-11-28 15:59       ` [Intel-gfx] " Ville Syrjälä
2019-11-29  8:48       ` Maarten Lankhorst
2019-11-29  8:48         ` [Intel-gfx] " Maarten Lankhorst
2019-11-29 11:37         ` Ville Syrjälä
2019-11-29 11:37           ` [Intel-gfx] " Ville Syrjälä
2019-12-03  8:45           ` Maarten Lankhorst
2019-12-03  8:45             ` [Intel-gfx] " Maarten Lankhorst
2019-12-03 13:04             ` Ville Syrjälä
2019-12-09 14:17     ` Ville Syrjälä
2019-11-27 23:15 ` ✗ Fi.CI.BAT: failure for drm/i915/fbc: Fix FBC for glk+ (rev4) Patchwork
2019-11-27 23:15   ` [Intel-gfx] " Patchwork
2019-11-28  1:33 ` [PATCH v2 00/14] drm/i915/fbc: Fix FBC for glk+ Daniel Drake
2019-11-28  1:33   ` [Intel-gfx] " Daniel Drake
2019-11-28 18:02 ` ✓ Fi.CI.BAT: success for drm/i915/fbc: Fix FBC for glk+ (rev5) Patchwork
2019-11-28 18:02   ` [Intel-gfx] " Patchwork
2019-11-29 23:51 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-29 23:51   ` [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=20191129183458.128AD2176D@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=drake@endlessm.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jian-hong@endlessm.com \
    --cc=paulo.r.zanoni@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@linux.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.