Thread (3 messages) flat view 3 messages, 2 authors, 2016-08-03

Re: [Intel-gfx] [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_l

From: Jani Nikula <jani.nikula@linux.intel.com>
Date: 2016-08-03 08:42:28
Also in: intel-gfx

On Tue, 02 Aug 2016, Sedat Dilek [off-list ref] wrote:
On Mon, Aug 1, 2016 at 3:33 PM, Jani Nikula [off-list ref] wrote:
quoted
On Fri, 15 Jul 2016, Sedat Dilek [off-list ref] wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help