From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: daniel.vetter@ffwll.ch
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
przanoni@gmail.com, airlied@linux.ie,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [v3.10][v3.11][v3.12][Regression][PATCH 0/1] Revert "Revert "drm/i915: revert eDP bpp clamping code changes""
Date: Wed, 16 Oct 2013 16:34:56 -0400 [thread overview]
Message-ID: <cover.1381939165.git.joseph.salisbury@canonical.com> (raw)
Hi Daniel,
A bug was opened against the Ubuntu kernel[0]. It was found that reverting the following commit resolved this bug:
commit 657445fe8660100ad174600ebfa61536392b7624
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Sat May 4 10:09:18 2013 +0200
Revert "drm/i915: revert eDP bpp clamping code changes"
The regression was introduced as of v3.10-rc2 and affects a large number of end users.
I see this code has gone back and forth a few times, so I was wondering if we could get some feedback. The revert of commit 657445f was tested aginst 3.11 stable and could not be done cleanly, so I had to make some modifications. The modifications I made for 3.11 are in [PATCH 1/1]. The revert can't be done cleanly against 3.12 neither. The modifications I made for 3.11 will not work cleanly on 3.12 due to recent changes in 3.12, such as commit 7984211. However, I can create a patch specific for 3.12 if you think this is the best way to go.
Thanks,
Joe
http://pad.lv/1195483
Joseph Salisbury (1):
Revert "Revert "drm/i915: revert eDP bpp clamping code changes""
drivers/gpu/drm/i915/intel_dp.c | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-10-16 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 20:34 Joseph Salisbury [this message]
2013-10-16 20:34 ` [v3.10][v3.11][v3.12][Regression][PATCH 1/1] Revert "Revert "drm/i915: revert eDP bpp clamping code changes"" 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 16:57 ` [Intel-gfx] " Josh Boyer
2013-10-31 16:57 ` Josh Boyer
2013-10-31 17:01 ` Jani Nikula
2013-10-31 17:01 ` Jani Nikula
2013-10-31 17:11 ` Josh Boyer
2013-10-31 17:11 ` [Intel-gfx] " 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=cover.1381939165.git.joseph.salisbury@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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 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.