From: Andi Kleen <andi@firstfloor.org>
To: John Hughes <john@Calva.COM>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: Am I allowed to call request_firmware_nowait from an interrupt handler?
Date: Mon, 20 Apr 2009 15:11:48 +0200 [thread overview]
Message-ID: <20090420131148.GY14687@one.firstfloor.org> (raw)
In-Reply-To: <49EC7200.9080308@Calva.COM>
On Mon, Apr 20, 2009 at 03:00:48PM +0200, John Hughes wrote:
> Andi Kleen wrote:
> >John Hughes <john@Calva.COM> writes:
> >
> >>Am I being a naughty boy?
> >>
> >
> >Yes.
> >
> >
> Buggeration. What an irritating restriction.
>
> So I'll have to make a thread to do the firmware download, in which case
> I can just use request_firmware instead of request_firmware_nowait.
>
> Or can I use schedule_work?
That's what it is for yes.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-04-20 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 11:47 Am I allowed to call request_firmware_nowait from an interrupt handler? John Hughes
2009-04-20 11:59 ` Andi Kleen
2009-04-20 13:00 ` John Hughes
2009-04-20 13:11 ` Andi Kleen [this message]
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=20090420131148.GY14687@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=john@Calva.COM \
--cc=linux-kernel@vger.kernel.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