Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758397AbZC3Sn2 (ORCPT ); Mon, 30 Mar 2009 14:43:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758420AbZC3Smz (ORCPT ); Mon, 30 Mar 2009 14:42:55 -0400 Received: from mail-bw0-f169.google.com ([209.85.218.169]:60560 "EHLO mail-bw0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758505AbZC3Smy convert rfc822-to-8bit (ORCPT ); Mon, 30 Mar 2009 14:42:54 -0400 MIME-Version: 1.0 In-Reply-To: References: <49CF9BA1.5030400@archlinux.org> <20090329091148.16a618bf@infradead.org> <49CFA436.5080000@archlinux.org> <49CFB553.1020800@archlinux.org> Date: Mon, 30 Mar 2009 20:42:36 +0200 Message-ID: Subject: Re: fastboot/async and initramfs: How am I supposed to know when devices are finished initializing? From: Kay Sievers To: Dan Williams Cc: =?UTF-8?Q?Thomas_B=C3=A4chler?= , Arjan van de Ven , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 631 Lines: 18 On Mon, Mar 30, 2009 at 20:23, Dan Williams wrote: > settle: allow --timeout=0 to test for "queue busy" > +       if (!udev_queue_get_queue_is_empty(udev_queue)) > +               rc = 1; You mean, we should not wait? Then we need to check for timeout == 0 and return immediately instead of entering the checking loop at all, right? Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/