Hi Greg, We've started to analize the list of upstream commits that have been backported to 3.2 but missing from 3.4. For the 12 commits that I've analized, - 2 commits were marked for stable but can't be applied cleanly to 3.4. - 2 commits were marked for stable but only affect 3.7+, don't know why it went into 3.2.x, and one of them was reverted in 3.2 stable. (*) - 1 commit 59bebf6c060b(in 3.2) fixed the previous patch f3825cc9679a(in 3.2). - 1 commit was marked for stable but not a 3.4 bug.(**) - 6 commits have no stable tag. I've found out why they were backported to 3.2.x, and I'm sure they shoud be applied to 3.4.x. There're 5 other commits that need trivial context adjustments. I'll send out the backports. Please apply them after the following patch: f76bb07cf0f7 drm/i915: panel: invert brightness via parameter Please cherry-pick those commits from 3.2.x: 87ae8984bd9c drm/i915; Only increment the user-pin-count after successfully pinning the bo f3825cc9679a drm/i915: dump UTS_RELEASE into the error_state 59bebf6c060b drm/i915: add missing \n to UTS_RELEASE in the error_state f76bb07cf0f7 drm/i915: panel: invert brightness via parameter (*)The commits are a2d2dcd9e1aa drm/i915: Disable AsyncFlip performance optimisations 393143615d9f drm/i915: GFX_MODE Flush TLB Invalidate Mode must be '1' for scanline waits (reverted in 3.2) (**) 8474b1ab89e4 drm/radeon: fix a rare case of double kfree Documentation/kernel-parameters.txt | 14 ++++++++++++++ drivers/gpu/drm/i915/i915_debugfs.c | 2 ++ drivers/gpu/drm/i915/i915_drv.h | 3 ++- drivers/gpu/drm/i915/i915_gem.c | 7 ++++--- drivers/gpu/drm/i915/intel_display.c | 22 ++++++++++++++++++++++ drivers/gpu/drm/i915/intel_panel.c | 24 ++++++++++++++++++++++++ 6 files changed, 68 insertions(+), 4 deletions(-) -- 1.8.2.2 -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html