On Wed, 29 Mar 2017, Jani Nikula wrote:
> On Tue, 21 Mar 2017, Jani Nikula wrote:
>> On Mon, 13 Mar 2017, Jani Nikula wrote:
>>> I'm already scripting my fixes backports quite a bit, and frankly don't
>>> really manually backport anything that doesn't apply cleanly. I'm
>>> thinking of automatin
On Wed, 29 Mar 2017, Chris Wilson wrote:
> On Wed, Mar 29, 2017 at 01:45:38PM +0300, Jani Nikula wrote:
>> On Tue, 21 Mar 2017, Jani Nikula wrote:
>> > On Mon, 13 Mar 2017, Jani Nikula wrote:
>> >> I'm already scripting my fixes backports quite a bit, and frankly don't
>> >> really manually back
On Wed, Mar 29, 2017 at 01:45:38PM +0300, Jani Nikula wrote:
> On Tue, 21 Mar 2017, Jani Nikula wrote:
> > On Mon, 13 Mar 2017, Jani Nikula wrote:
> >> I'm already scripting my fixes backports quite a bit, and frankly don't
> >> really manually backport anything that doesn't apply cleanly. I'm
>
On Tue, 21 Mar 2017, Jani Nikula wrote:
> On Mon, 13 Mar 2017, Jani Nikula wrote:
>> I'm already scripting my fixes backports quite a bit, and frankly don't
>> really manually backport anything that doesn't apply cleanly. I'm
>> thinking of automating some "failed to backport" reporting to author
On Tue, 21 Mar 2017, Chris Wilson wrote:
> On Tue, Mar 21, 2017 at 04:23:19PM +0200, Jani Nikula wrote:
>> On Mon, 13 Mar 2017, Jani Nikula wrote:
>> > I'm already scripting my fixes backports quite a bit, and frankly don't
>> > really manually backport anything that doesn't apply cleanly. I'm
>>
On Tue, Mar 21, 2017 at 04:23:19PM +0200, Jani Nikula wrote:
> On Mon, 13 Mar 2017, Jani Nikula wrote:
> > I'm already scripting my fixes backports quite a bit, and frankly don't
> > really manually backport anything that doesn't apply cleanly. I'm
> > thinking of automating some "failed to backpo
On Mon, 13 Mar 2017, Jani Nikula wrote:
> I'm already scripting my fixes backports quite a bit, and frankly don't
> really manually backport anything that doesn't apply cleanly. I'm
> thinking of automating some "failed to backport" reporting to authors,
> not unlike the failed stable backport rep
On Wed, Mar 15, 2017 at 11:24:43AM +0200, Jani Nikula wrote:
> On Mon, 13 Mar 2017, Chris Wilson wrote:
> > On Mon, Mar 13, 2017 at 06:14:56PM +0200, Jani Nikula wrote:
> >> a5509abda48e ("drm/i915: Fix legacy cursor vs. watermarks for ILK-BDW")
> >> 5be6e3340099 ("drm/i915: Do .init_clock_gating(
On Mon, 13 Mar 2017, Chris Wilson wrote:
> On Mon, Mar 13, 2017 at 06:14:56PM +0200, Jani Nikula wrote:
>> 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?
Ville,
On Tue, 14 Mar 2017, Jani Nikula wrote:
> 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.
I sent the fixes pull request for -rc3, and pushed Chris' backports
after that, thanks again.
I c
On Mon, 13 Mar 2017, Chris Wilson 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?
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?
> 262fd485ac6b ("drm/i915: Only enable hotplug inte
I'm already scripting my fixes backports quite a bit, and frankly don't
really manually backport anything that doesn't apply cleanly. I'm
thinking of automating some "failed to backport" reporting to authors,
not unlike the failed stable backport reports.
This is a manual report that the followin
13 matches
Mail list logo
