All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "pebolle@tiscali.nl" <pebolle@tiscali.nl>,
	"James.Bottomley@HansenPartnership.com" 
	<James.Bottomley@HansenPartnership.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] screen freeze with 5.2-rc6 Dell XPS-13 skylake i915
Date: Fri, 9 Aug 2019 17:16:03 +0000	[thread overview]
Message-ID: <54f0979debcd4459ca9d9f25941d4fa29a1aab06.camel@intel.com> (raw)
In-Reply-To: <df4d83e5c5650ea2f1afde1469c9dc82d6120644.camel@tiscali.nl>

Fix released on Linux 5.2.8

On Wed, 2019-07-24 at 22:39 +0200, Paul Bolle wrote:
> Hi Jose,
> 
> Souza, Jose schreef op wo 24-07-2019 om 20:27 [+0000]:
> > We fixed the patch instead of revert it, it is merged on drm-tip
> > and on
> > his way to linux-stable.
> 
> That should be (drm-tip) commit b5ea9c933700 ("drm/i915/vbt: Fix VBT
> parsing
> for the PSR section"). Correct?
> 
> > Huge thanks again
> 
> You're welcome.
> 
> 
> Paul Bolle
> 

  parent reply	other threads:[~2019-08-09 17:16 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-29 18:56 screen freeze with 5.2-rc6 Dell XPS-13 skylake i915 James Bottomley
2019-07-09 13:52 ` Paul Bolle
2019-07-10 15:01 ` James Bottomley
2019-07-10 16:16   ` Paul Bolle
2019-07-10 16:32     ` James Bottomley
2019-07-10 16:32       ` James Bottomley
2019-07-10 16:45       ` Paul Bolle
2019-07-10 16:45         ` Paul Bolle
2019-07-10 17:35         ` James Bottomley
2019-07-10 21:59           ` Paul Bolle
2019-07-10 22:18             ` James Bottomley
2019-07-11 19:32               ` [Intel-gfx] " Souza, Jose
2019-07-11 19:32                 ` Souza, Jose
2019-07-11  9:29 ` Chris Wilson
2019-07-11 11:20   ` Paul Bolle
2019-07-11 11:20     ` Paul Bolle
2019-07-12 10:32     ` Paul Bolle
2019-07-11 20:11   ` James Bottomley
2019-07-11 20:25     ` [Intel-gfx] " Souza, Jose
2019-07-11 20:25       ` Souza, Jose
2019-07-11 20:28       ` [Intel-gfx] " James Bottomley
2019-07-11 21:57         ` James Bottomley
2019-07-11 22:26           ` Souza, Jose
2019-07-11 22:26             ` Souza, Jose
2019-07-11 22:38             ` James Bottomley
2019-07-11 23:03               ` Paul Bolle
2019-07-11 23:28                 ` Souza, Jose
2019-07-11 23:28                   ` Souza, Jose
2019-07-11 23:40                   ` James Bottomley
2019-07-11 23:40                     ` James Bottomley
2019-07-12 14:19                     ` [Intel-gfx] " James Bottomley
2019-07-12 14:19                       ` James Bottomley
2019-07-12 14:28                       ` [Intel-gfx] " Paul Bolle
2019-07-15 21:03                         ` Souza, Jose
2019-07-15 21:03                           ` Souza, Jose
2019-07-15 21:34                           ` [Intel-gfx] " Paul Bolle
2019-07-15 21:34                             ` Paul Bolle
2019-07-16 16:32                             ` [Intel-gfx] " Souza, Jose
2019-07-16 16:32                               ` Souza, Jose
2019-07-17 21:27                               ` Paul Bolle
2019-07-17 21:27                                 ` Paul Bolle
2019-07-17 21:29                                 ` James Bottomley
2019-07-24 19:23                                   ` Paul Bolle
2019-07-24 20:27                                     ` Souza, Jose
2019-07-24 20:27                                       ` Souza, Jose
2019-07-24 20:39                                       ` [Intel-gfx] " Paul Bolle
2019-07-24 20:39                                         ` Paul Bolle
2019-07-24 20:42                                         ` Souza, Jose
2019-07-24 20:42                                           ` Souza, Jose
2019-08-09 17:16                                         ` Souza, Jose [this message]
2019-08-09 17:16                                           ` Souza, Jose
2019-08-10 19:40                                           ` Paul Bolle

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=54f0979debcd4459ca9d9f25941d4fa29a1aab06.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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.