mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: "Thomas Bächler" <thomas@archlinux.org>,
	"Arjan van de Ven" <arjan@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: fastboot/async and initramfs: How am I supposed to know when  devices are finished initializing?
Date: Mon, 30 Mar 2009 12:08:07 -0700	[thread overview]
Message-ID: <e9c3a7c20903301208k6fe17c92xe855a3c85d893454@mail.gmail.com> (raw)
In-Reply-To: <ac3eb2510903301142h21dec2eajd03057095aa4f11c@mail.gmail.com>

On Mon, Mar 30, 2009 at 11:42 AM, Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Mon, Mar 30, 2009 at 20:23, Dan Williams <dan.j.williams@intel.com> 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?
>

We already skip if loop==0...?

</me checks latest git>

Oh, this patch (against 138) needs to be reworked.

Thanks,
Dan

  reply	other threads:[~2009-03-30 19:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29 16:02 Thomas Bächler
2009-03-29 16:11 ` Arjan van de Ven
2009-03-29 16:39   ` Thomas Bächler
2009-03-29 17:36     ` Kay Sievers
2009-03-29 17:52       ` Thomas Bächler
2009-03-29 18:06         ` Kay Sievers
2009-03-30 18:23           ` Dan Williams
2009-03-30 18:42             ` Kay Sievers
2009-03-30 19:08               ` Dan Williams [this message]
2009-03-29 20:03         ` fastboot/async and initramfs: How am I supposed to know when?devices " Alexander Clouter
2009-03-30 20:20           ` Thomas Bächler
     [not found]   ` <49CFA2CC.9080506@archlinux.org>
     [not found]     ` <20090329094220.4e80c267@infradead.org>
2009-03-29 17:23       ` fastboot/async and initramfs: How am I supposed to know when devices " Thomas Bächler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e9c3a7c20903301208k6fe17c92xe855a3c85d893454@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=arjan@infradead.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@archlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®