From: Jani Nikula <jani.nikula@linux.intel.com>
To: sedat.dilek@gmail.com
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
linux-fbdev@vger.kernel.org
Subject: Re: [Intel-gfx] [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_l
Date: Wed, 03 Aug 2016 08:42:25 +0000 [thread overview]
Message-ID: <87twf2qm4u.fsf@intel.com> (raw)
In-Reply-To: <CA+icZUU2Q7e5rthM9+ydPM5EtROufY1wVmg-MvKwGbPq=o3a0A@mail.gmail.com>
On Tue, 02 Aug 2016, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> On Mon, Aug 1, 2016 at 3:33 PM, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>> On Fri, 15 Jul 2016, Sedat Dilek <sedat.dilek@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
prev parent reply other threads:[~2016-08-03 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+icZUUUUCybFnneuhVVT4Z_vymMcLp4HdCe3CDY5SerFnP+tg@mail.gmail.com>
2016-07-15 8:40 ` [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || Chris Wilson
2016-07-15 10:37 ` Sedat Dilek
2016-08-17 19:27 ` Sedat Dilek
2016-08-17 19:36 ` Johannes Berg
2016-08-01 13:33 ` [Intel-gfx] [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_l Jani Nikula
2016-08-02 17:47 ` Sedat Dilek
2016-08-03 8:42 ` Jani Nikula [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twf2qm4u.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=sedat.dilek@gmail.com \
--cc=tomi.valkeinen@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).