<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@drv_selftest@mock_breadcrumbs - breadcrumbs returned 10000, conflicting with selftest's magic values!" href="https://bugs.freedesktop.org/show_bug.cgi?id=106085#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@drv_selftest@mock_breadcrumbs - breadcrumbs returned 10000, conflicting with selftest's magic values!" href="https://bugs.freedesktop.org/show_bug.cgi?id=106085">bug 106085</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>For reference, commit d224985a5e312ab05b624143a3fd9bb91b53e52a Author: Peter Zijlstra <<a href="mailto:peterz@infradead.org">peterz@infradead.org</a>> Date: Thu Mar 15 11:41:39 2018 +0100 sched/wait, drivers/drm: Convert wait_on_atomic_t() usage to the new wait_var_event() API The old wait_on_atomic_t() is going to get removed, use the more flexible wait_var_event() API instead. Unlike wake_up_atomic_t(), wake_up_var() will issue the wakeup even if the variable is not 0. No change in functionality. Signed-off-by: Peter Zijlstra (Intel) <<a href="mailto:peterz@infradead.org">peterz@infradead.org</a>> Reviewed-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Cc: Daniel Vetter <<a href="mailto:daniel.vetter@intel.com">daniel.vetter@intel.com</a>> Cc: David Airlie <<a href="mailto:airlied@linux.ie">airlied@linux.ie</a>> Cc: Linus Torvalds <<a href="mailto:torvalds@linux-foundation.org">torvalds@linux-foundation.org</a>> Cc: Mike Galbraith <<a href="mailto:efault@gmx.de">efault@gmx.de</a>> Cc: Peter Zijlstra <<a href="mailto:peterz@infradead.org">peterz@infradead.org</a>> Cc: Thomas Gleixner <<a href="mailto:tglx@linutronix.de">tglx@linutronix.de</a>> Cc: <a href="mailto:linux-kernel@vger.kernel.org">linux-kernel@vger.kernel.org</a> Signed-off-by: Ingo Molnar <<a href="mailto:mingo@kernel.org">mingo@kernel.org</a>> did impact upon mock_breadcrumbs. Whether that alone is the cause...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>