dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Joseph Salisbury <joseph.salisbury@canonical.com>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	przanoni@gmail.com, Dave Airlie <airlied@linux.ie>,
	intel-gfx@lists.freedesktop.org,
	DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [v3.10][v3.11][v3.12][Regression][PATCH 1/1] Revert "Revert "drm/i915: revert eDP bpp clamping code changes""
Date: Thu, 31 Oct 2013 19:01:16 +0200	[thread overview]
Message-ID: <87txfxml2b.fsf@intel.com> (raw)
In-Reply-To: <CA+5PVA7j+90_iwZD+Gx9cAuqwEGH+cKB98OQj2+w4fhC_JT0pw@mail.gmail.com>

On Thu, 31 Oct 2013, Josh Boyer <jwboyer@fedoraproject.org> wrote:
> On Thu, Oct 31, 2013 at 10:58 AM, Jani Nikula
> <jani.nikula@linux.intel.com> wrote:
>> On Fri, 25 Oct 2013, Joseph Salisbury <joseph.salisbury@canonical.com> wrote:
>>> On 10/16/2013 05:02 PM, Daniel Vetter wrote:
>>>> It's by far not that simple. Jani is working on both the underlying bug
>>>> and a better w/a. See
>>>>
>>>> https://bugzilla.kernel.org/show_bug.cgi?id=59841
>>>>
>>>> for the full story in its entire glory.
>>>>
>>>> Cheers, Daniel
>>>
>>> Thanks for the feedback, Daniel.  Is there an estimate on what mainline
>>> release might contain Jani's work?
>>
>> commit c6cd2ee2d59111a07cd9199564c9bdcb2d11e5cf
>> Author: Jani Nikula <jani.nikula@intel.com>
>> Date:   Mon Oct 21 10:52:07 2013 +0300
>>
>>     drm/i915/dp: workaround BIOS eDP bpp clamping issue
>>
>> and a couple of dependencies are now in Linus' tree, i.e. should be
>> released in 3.12. The commits are also CC: stable.
>
> Are the dependency commits you mentioned these?

Yes; sorry for not mentioning them explicitly.

BR,
Jani.


> commit 7195a50b5c7e00cc3312934fd022c3006b533d12
> Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Date:   Tue Sep 24 14:24:05 2013 +0300
>
>     drm/i915: Add HSW CRT output readout support
>
> commit 4f56d12ebb28fceac4c6e60c8993fbfc122e1399
> Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Date:   Mon Oct 21 10:52:06 2013 +0300
>
>     drm/i915: Add support for pipe_bpp readout
>
> josh

-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2013-10-31 17:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 20:34 [v3.10][v3.11][v3.12][Regression][PATCH 0/1] Revert "Revert "drm/i915: revert eDP bpp clamping code changes"" Joseph Salisbury
2013-10-16 20:34 ` [v3.10][v3.11][v3.12][Regression][PATCH 1/1] " Joseph Salisbury
2013-10-16 21:02   ` Daniel Vetter
2013-10-25 15:36     ` Joseph Salisbury
2013-10-31 14:58       ` [Intel-gfx] " Jani Nikula
2013-10-31 16:41         ` Joseph Salisbury
2013-10-31 16:57         ` Josh Boyer
2013-10-31 17:01           ` Jani Nikula [this message]
2013-10-31 17:11             ` Josh Boyer

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=87txfxml2b.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joseph.salisbury@canonical.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=przanoni@gmail.com \
    --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).