From: Kay Sievers <kay.sievers@vrfy.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Tomas Winkler <tomasw@gmail.com>, Greg KH <greg@kroah.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] firmware class: export nowait to userspace
Date: Fri, 12 Mar 2010 06:29:58 +0100 [thread overview]
Message-ID: <ac3eb2511003112129i2274b018m7e059f348d5f983a@mail.gmail.com> (raw)
In-Reply-To: <1268369163.4828.1.camel@jlt3.sipsolutions.net>
On Fri, Mar 12, 2010 at 05:46, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Fri, 2010-03-12 at 05:21 +0100, Kay Sievers wrote:
>> The firmware_class already always exports a TIMEOUT= value, right? If
>> this is the case, it should be set to 0, I guess.
>
> Yes and no. It is exported, but typically it will be 60 seconds. And
> even in this case it makes sense to eventually time out when userspace
> is not responding.
Ok, I didn't expect the async version to time out. Sounds fine then.
>> Sounds fine to have a flag like this, while "NOWAIT" is, I guess, a
>> pretty bad name from the event perspective. This name might make sense
>> for the called kernel function, but not so much for a firmware loader
>> instruction.
>
> Yeah, I can agree with that. How about "ASYNC" or so? It needs to
> distinguish between "I'm going to wait for this please respond" and "I'm
> not really waiting, please let me now when you can".
Yeah, sounds fine to me.
Thanks,
Kay
next prev parent reply other threads:[~2010-03-12 5:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 22:39 firmware loading vs. initrd Johannes Berg
2010-03-11 22:56 ` [PATCH] firmware class: export nowait to userspace Johannes Berg
2010-03-12 4:21 ` Kay Sievers
2010-03-12 4:46 ` Johannes Berg
2010-03-12 5:29 ` Kay Sievers [this message]
2010-03-29 15:57 ` Johannes Berg
2010-03-12 4:32 ` firmware loading vs. initrd Kay Sievers
2010-03-12 4:48 ` Johannes Berg
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=ac3eb2511003112129i2274b018m7e059f348d5f983a@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tomasw@gmail.com \
/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®