Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751241AbcL1JEh (ORCPT ); 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 ); 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" To: "sedat.dilek@gmail.com" , Chris Wilson , "Wysocki, Rafael J" , Thomas Gleixner , intel-gfx , Linux PM List , LKML , the arch/x86 maintainers CC: Daniel Vetter 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: <20161227102442.GA1717@nuc-i3427.alporthouse.com> <20161227151001.GJ31952@dvetter-linux.ger.corp.intel.com> In-Reply-To: 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: 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 ; Sedat Dilek > ; Wysocki, Rafael J ; > Thomas Gleixner ; intel-gfx gfx@lists.freedesktop.org>; Linux PM List foundation.org>; LKML ; the arch/x86 > maintainers > Cc: Daniel Vetter > 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