RE: [Intel-gfx] [Linux v4.10.0-rc1] call-traces after suspend-resume (pm? i915? cpu/hotplug?)

[Saarinen, Jani]

HI, 
> -----Original Message-----
> From: Intel-gfx [mailto:intel-gfx-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf
> Of Sedat Dilek
> Sent: Tuesday, December 27, 2016 6:07 PM
> To: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>; Sedat Dilek
> <sedat.dilek@xxxxxxxxx>; Wysocki, Rafael J <rafael.j.wysocki@xxxxxxxxx>;
> Thomas Gleixner <tglx@xxxxxxxxxxxxx>; intel-gfx <intel-
> gfx@xxxxxxxxxxxxxxxxxxxxx>; Linux PM List <linux-pm@xxxxxxxxxxxx
> foundation.org>; LKML <linux-kernel@xxxxxxxxxxxxxxx>; the arch/x86
> maintainers <x86@xxxxxxxxxx>
> Cc: Daniel Vetter <daniel.vetter@xxxxxxxx>
> 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