[Intel-gfx] [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || __blocking_notifier_call_chain

[Jani Nikula]

On Tue, 02 Aug 2016, Sedat Dilek <sedat.dilek at gmail.com> wrote:
> On Mon, Aug 1, 2016 at 3:33 PM, Jani Nikula <jani.nikula at linux.intel.com> wrote:
>> On Fri, 15 Jul 2016, Sedat Dilek <sedat.dilek at gmail.com> wrote:
>>> Hi,
>>>
>>> I see the below call-trace with latest d-i-n, guess latest linux-next
>>
>> FWIW, "d-i-n" is ambiguous (drm-intel-next vs. drm-intel-nightly) and we
>> don't use that ourselves.
>>
>
> Oh, sorry with d-i-n I meant drm-intel-nightly.
> Normally, I also point to the "integration manifest"
> like...drm-intel-nightly: 2016y-08m-02d-14h-10m-12s UTC integration
> manifest.
> You do not test d-i-n yourself?
> Strange.

We do not use the *acronym* "d-i-n" ourselves because it is
ambiguous. drm-intel-nightly is our main test target.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center