From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: linux-next: Tree for Jan 25 (BROKEN suspend) Date: Mon, 28 Jan 2013 11:28:07 -0800 Message-ID: <20130128192807.GF22465@mtj.dyndns.org> References: <18624541.r6CtJttOWZ@vostro.rjw.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-qa0-f47.google.com ([209.85.216.47]:60729 "EHLO mail-qa0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751977Ab3A1T2M (ORCPT ); Mon, 28 Jan 2013 14:28:12 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Sedat Dilek Cc: "Rafael J. Wysocki" , Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Linux PM List , Linux ACPI , Sasha Levin Hello, guys. On Sun, Jan 27, 2013 at 02:01:50PM +0100, Sedat Dilek wrote: > OK, that bisecting ruined a bit my weekend and showed me again you > cannot really bisect Linux-Next. > Sometimes, it is better not to trust the tools blindly and do a > bisect-on-suspicion. > Anyway... cultprit found... patch found... applied... all GOOD now. > ( If I had waited for next Monday's next-20130127 I would not have > seen what caused the trouble. ). Yeah, my usual test setup didn't have async tasks w/o domain so I failed to notice the breakage. Sorry about the trouble guys and lots of thanks to Sedat for the firefighting over the weekend. :) -- tejun