From: "Souza, Jose" <jose.souza@intel.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Cc: "sashal@kernel.org" <sashal@kernel.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH stable v5.2] drm/i915/vbt: Fix VBT parsing for the PSR section
Date: Wed, 24 Jul 2019 17:27:42 +0000 [thread overview]
Message-ID: <05339e812e35a4cf1811f26a06bd5a4d1d652407.camel@intel.com> (raw)
In-Reply-To: <20190724120657.GG3244@kroah.com>
On Wed, 2019-07-24 at 14:06 +0200, Greg KH wrote:
> On Mon, Jul 22, 2019 at 04:13:25PM -0700, Dhinakaran Pandiyan wrote:
> > A single 32-bit PSR2 training pattern field follows the sixteen
> > element
> > array of PSR table entries in the VBT spec. But, we incorrectly
> > define
> > this PSR2 field for each of the PSR table entries. As a result, the
> > PSR1
> > training pattern duration for any panel_type != 0 will be parsed
> > incorrectly. Secondly, PSR2 training pattern durations for VBTs
> > with bdb
> > version >= 226 will also be wrong.
> >
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: José Roberto de Souza <jose.souza@intel.com>
> > Cc: stable@vger.kernel.org
> > Cc: stable@vger.kernel.org #v5.2
> > Fixes: 88a0d9606aff ("drm/i915/vbt: Parse and use the new field
> > with PSR2 TP2/3 wakeup time")
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111088
> > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204183
> > Signed-off-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> > Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
> > Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Tested-by: François Guerraz <kubrick@fgv6.net>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Link:
> > https://patchwork.freedesktop.org/patch/msgid/20190717223451.2595-1-dhinakaran.pandiyan@intel.com
> > (cherry picked from commit
> > b5ea9c9337007d6e700280c8a60b4e10d070fb53)
>
> There is no such commit in Linus's kernel tree :(
>
It is still on drm-intel/drm-intel-next-queued -
ssh://git.freedesktop.org/git/drm-intel
Rodrigo do you know when is the next pull-request to Linus?
next prev parent reply other threads:[~2019-07-24 17:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 22:34 [PATCH] drm/i915/vbt: Fix VBT parsing for the PSR section Dhinakaran Pandiyan
2019-07-18 19:14 ` [Intel-gfx] " Rodrigo Vivi
[not found] ` <20190719004526.B0CC521850@mail.kernel.org>
2019-07-22 23:13 ` [PATCH stable v5.2] " Dhinakaran Pandiyan
2019-07-24 12:06 ` Greg KH
2019-07-24 17:27 ` Souza, Jose [this message]
2019-07-24 17:40 ` [Intel-gfx] " Rodrigo Vivi
2019-07-30 15:19 ` Rodrigo Vivi
2019-07-30 15:27 ` Greg KH
2019-07-30 16:22 ` Rodrigo Vivi
2019-07-30 16:27 ` Greg KH
2019-07-30 16:56 ` Rodrigo Vivi
2019-07-30 17:08 ` Greg KH
2019-07-30 18:24 ` Pandiyan, Dhinakaran
2019-07-30 20:42 ` [Intel-gfx] [PATCH] " Rodrigo Vivi
2019-07-30 21:48 ` Sasha Levin
2019-07-31 17:14 ` Vivi, Rodrigo
2019-07-31 19:23 ` Sasha Levin
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=05339e812e35a4cf1811f26a06bd5a4d1d652407.camel@intel.com \
--to=jose.souza@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=sashal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).