Re: Fixes that failed to backport to v4.11-rc1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 13 Mar 2017, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote:
> On Mon, Mar 13, 2017 at 06:14:56PM +0200, Jani Nikula wrote:
>> 1f7b847d72c3 ("drm/i915: Disable engine->irq_tasklet around resets")
> Done.
>
>> 370a81fb89cb ("drm/i915: Remove unused function intel_ddi_get_link_dpll()")
> Don't bother, just code tidy?

Agreed; I didn't look at or filter the list at all before sending.

>
>> 262fd485ac6b ("drm/i915: Only enable hotplug interrupts if the display interrupts are enabled")
> Done
>
>> ef0f411f5147 ("drm/i915: Drop support for I915_EXEC_CONSTANTS_* execbuf parameters.")
> Done.
>
>> c998e8a0f43a ("drm/i915: Hold rpm during GEM suspend in driver unload/suspend")
> No one else has noticed, so user impact is zero.
>
>> a5509abda48e ("drm/i915: Fix legacy cursor vs. watermarks for ILK-BDW")
>> 5be6e3340099 ("drm/i915: Do .init_clock_gating() earlier to avoid it clobbering watermarks")
>
> Ville?
>
>> d9321a03efcd ("drm/i915/glk: Remove MODULE_FIRMWARE() tag from Geminilake's DMC")
>
> Jani, I'd say that's your call as to whether it make sense to backport a
> minor user confusion fix.

This causes initrd tools to whine if the firmware is missing. I think we
want this.

Thank you for the backports. I'll likely send a pull request of the
stuff I have in -fixes now, apply these, and let them simmer until next
week's pull.

BR,
Jani.

>
>> e0e8c7cb6eb6 ("drm/i915: Stop using RP_DOWN_EI on Baytrail")
> Done.
> -Chris

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx




[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux