Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751241AbcL1JEh (ORCPT <rfc822;w@1wt.eu>);
        Wed, 28 Dec 2016 04:04:37 -0500
Received: from mga04.intel.com ([192.55.52.120]:49810 "EHLO mga04.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751103AbcL1JEf (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 28 Dec 2016 04:04:35 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.33,421,1477983600"; 
   d="scan'208";a="1105155902"
From: "Saarinen, Jani" <jani.saarinen@intel.com>
To: "sedat.dilek@gmail.com" <sedat.dilek@gmail.com>,
        Chris Wilson <chris@chris-wilson.co.uk>,
        "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        intel-gfx <intel-gfx@lists.freedesktop.org>,
        Linux PM List <linux-pm@lists.linux-foundation.org>,
        LKML <linux-kernel@vger.kernel.org>,
        the arch/x86 maintainers <x86@kernel.org>
CC: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: RE: [Intel-gfx] [Linux v4.10.0-rc1] call-traces after
        suspend-resume (pm? i915? cpu/hotplug?)
Thread-Topic: [Intel-gfx] [Linux v4.10.0-rc1] call-traces after
        suspend-resume (pm? i915? cpu/hotplug?)
Thread-Index: AQHSYFm7jGTYakB7c0q0f4GrnqXkh6Eb9d0AgAEbT3A=
Date: Wed, 28 Dec 2016 09:04:29 +0000
Message-ID: <43D4F724E12AB6478FC1572B3FBE89D04C0D6A10@IRSMSX106.ger.corp.intel.com>
References: <CA+icZUVdjS8Wjjw5WxLZmv6JHV3ybFGnG8fi6TuafXDgGSV4SQ@mail.gmail.com>
 <20161227102442.GA1717@nuc-i3427.alporthouse.com>
 <20161227151001.GJ31952@dvetter-linux.ger.corp.intel.com>
 <CA+icZUVS+sT0WF7XMpc00iNbSugOz_fc-3-Rr=LNj-UkYiOR-Q@mail.gmail.com>
 <CA+icZUXqH6rw4n1u-vivPaZC5UViJrs3Q4iihFNEiweGNVVfAA@mail.gmail.com>
In-Reply-To: <CA+icZUXqH6rw4n1u-vivPaZC5UViJrs3Q4iihFNEiweGNVVfAA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [163.33.239.181]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id uBS94kuS013889
Content-Length: 1252
Lines: 32

HI, 
> -----Original Message-----
> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf
> Of Sedat Dilek
> Sent: Tuesday, December 27, 2016 6:07 PM
> To: Chris Wilson <chris@chris-wilson.co.uk>; Sedat Dilek
> <sedat.dilek@gmail.com>; Wysocki, Rafael J <rafael.j.wysocki@intel.com>;
> Thomas Gleixner <tglx@linutronix.de>; intel-gfx <intel-
> gfx@lists.freedesktop.org>; Linux PM List <linux-pm@lists.linux-
> foundation.org>; LKML <linux-kernel@vger.kernel.org>; the arch/x86
> maintainers <x86@kernel.org>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Subject: Re: [Intel-gfx] [Linux v4.10.0-rc1] call-traces after suspend-resume
> (pm? i915? cpu/hotplug?)
> 
> >> Also note that our CI is unhappy with -rc1, and it was not due to
> >> i915 patches. So very likely something else is also broken.
> >>
> >
> > Can you explain what "CI" means and its function in drm-intel development?
> >
See https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-intel.html (Pre-Merge Testing) and 
https://01.org/linuxgraphics/documentation/reproducing-patchwork-test-results
and (next link also on above documentation) https://intel-gfx-ci.01.org/CI/

Br

Jani Saarinen
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo