From: <gregkh@linuxfoundation.org>
To: l.stach@pengutronix.de, airlied@linux.ie, daniel.vetter@ffwll.ch,
daniel@ffwll.ch, fabio.estevam@nxp.com, festevam@gmail.com,
gregkh@linuxfoundation.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "drm/atomic: clear out fence when duplicating state" has been added to the 4.9-stable tree
Date: Fri, 27 Jan 2017 15:37:16 +0100 [thread overview]
Message-ID: <148552783625197@kroah.com> (raw)
In-Reply-To: <20170127103304.27613-1-l.stach@pengutronix.de>
This is a note to let you know that I've just added the patch titled
drm/atomic: clear out fence when duplicating state
to the 4.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
drm-atomic-clear-out-fence-when-duplicating-state.patch
and it can be found in the queue-4.9 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From l.stach@pengutronix.de Fri Jan 27 15:34:48 2017
From: Lucas Stach <l.stach@pengutronix.de>
Date: Fri, 27 Jan 2017 11:33:04 +0100
Subject: drm/atomic: clear out fence when duplicating state
To: David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org, stable@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>, Fabio Estevam <festevam@gmail.com>, kernel@pengutronix.de, patchwork-lst@pengutronix.de
Message-ID: <20170127103304.27613-1-l.stach@pengutronix.de>
From: Lucas Stach <l.stach@pengutronix.de>
[Fixed differently in 4.10]
The fence needs to be cleared out, otherwise the following commit
might wait on a stale fence from the previous commit. This was fixed
as a side effect of 9626014258a5 (drm/fence: add in-fences support)
in kernel 4.10.
As this commit introduces new functionality and as such can not be
applied to stable, this patch is the minimal fix for the kernel 4.9
stable series.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Tested-by: Fabio Estevam <fabio.estevam@nxp.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/gpu/drm/drm_atomic_helper.c | 2 ++
1 file changed, 2 insertions(+)
--- a/drivers/gpu/drm/drm_atomic_helper.c
+++ b/drivers/gpu/drm/drm_atomic_helper.c
@@ -3115,6 +3115,8 @@ void __drm_atomic_helper_plane_duplicate
if (state->fb)
drm_framebuffer_reference(state->fb);
+
+ state->fence = NULL;
}
EXPORT_SYMBOL(__drm_atomic_helper_plane_duplicate_state);
Patches currently in stable-queue which might be from l.stach@pengutronix.de are
queue-4.9/drm-atomic-clear-out-fence-when-duplicating-state.patch
prev parent reply other threads:[~2017-01-27 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 10:33 [PATCH] drm/atomic: clear out fence when duplicating state Lucas Stach
2017-01-27 10:33 ` Lucas Stach
2017-01-27 11:43 ` Fabio Estevam
2017-01-27 11:43 ` Fabio Estevam
2017-01-27 14:07 ` Daniel Vetter
2017-01-27 14:07 ` Daniel Vetter
2017-01-27 14:37 ` gregkh [this message]
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=148552783625197@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=l.stach@pengutronix.de \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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.