From: Greg KH <gregkh@linuxfoundation.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: chris@chris-wilson.co.uk, daniel.vetter@ffwll.ch,
gustav.fagerlind@gmail.com, weinan.z.li@intel.com,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "drm/i915: Fix races on fbdev" has been added to the 4.5-stable tree
Date: Sat, 4 Jun 2016 14:37:41 -0700 [thread overview]
Message-ID: <20160604213741.GA31906@kroah.com> (raw)
In-Reply-To: <20160604213824.GA17025@wunner.de>
On Sat, Jun 04, 2016 at 11:38:24PM +0200, Lukas Wunner wrote:
> On Sat, Jun 04, 2016 at 02:22:34PM -0700, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > drm/i915: Fix races on fbdev
> >
> > to the 4.5-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-i915-fix-races-on-fbdev.patch
> > and it can be found in the queue-4.5 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.
>
> That patch unfortunately turned out to cause deadlocks on suspend/resume
> on ILK, SNB and IVB in Intel's CI test farm (which I couldn't reproduce
> on my IVB machine and therefore couldn't debug). The commit was reverted
> upstream with 934458c2c95d.
>
> Therefore please do not apply it to stable kernels. My apologies for the
> inconvenience.
Now removed, thanks.
greg k-h
prev parent reply other threads:[~2016-06-04 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 21:22 Patch "drm/i915: Fix races on fbdev" has been added to the 4.5-stable tree gregkh
2016-06-04 21:38 ` Lukas Wunner
2016-06-04 21:37 ` Greg KH [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=20160604213741.GA31906@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=gustav.fagerlind@gmail.com \
--cc=lukas@wunner.de \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=weinan.z.li@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.