From: Greg KH <greg@kroah.com>
To: Abhay_Salunke@Dell.com
Cc: dtor_core@ameritech.net, linux-kernel@vger.kernel.org,
akpm@osdl.org, Matt_Domsch@Dell.com, ranty@debian.org
Subject: Re: [patch 2.6.12-rc3] modifications in firmware_class.c to support nohotplug
Date: Wed, 8 Jun 2005 09:26:32 -0700 [thread overview]
Message-ID: <20050608162632.GA1588@kroah.com> (raw)
In-Reply-To: <367215741E167A4CA813C8F12CE0143B3ED3B6@ausx2kmpc115.aus.amer.dell.com>
On Wed, Jun 08, 2005 at 11:23:30AM -0500, Abhay_Salunke@Dell.com wrote:
>
>
> > -----Original Message-----
> > From: Greg KH [mailto:greg@kroah.com]
> > Sent: Wednesday, June 08, 2005 11:10 AM
> > To: Salunke, Abhay
> > Cc: dtor_core@ameritech.net; linux-kernel@vger.kernel.org;
> akpm@osdl.org;
> > Domsch, Matt; ranty@debian.org
> > Subject: Re: [patch 2.6.12-rc3] modifications in firmware_class.c to
> > support nohotplug
> >
> > On Wed, Jun 08, 2005 at 11:04:09AM -0500, Abhay_Salunke@Dell.com
> wrote:
> > > > I think it would be better if you just have request_firmware and
> > > > request_firmware_nowait accept timeout parameter that would
> override
> > > > default timeout in firmware_class. 0 would mean use default,
> > > > MAX_SCHED_TIMEOUT - wait indefinitely.
> > >
> > > But we still need to avoid hotplug being invoked as we need it be a
> > > manual process.
> >
> > No, hotplug can happen just fine (it happens loads of times today for
> > things that people don't care about.)
> >
> If hotplug happens the complete function is called which makes the
> request_firmware return with a failure.
If this was true, then the current code would not work at all.
next prev parent reply other threads:[~2005-06-08 16:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 16:23 [patch 2.6.12-rc3] modifications in firmware_class.c to support nohotplug Abhay_Salunke
2005-06-08 16:26 ` Greg KH [this message]
2005-06-08 17:06 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2005-06-10 19:45 Abhay_Salunke
2005-06-10 19:57 ` Dmitry Torokhov
2005-06-09 21:11 Abhay_Salunke
2005-06-08 16:35 Abhay_Salunke
2005-06-08 16:04 Abhay_Salunke
2005-06-08 16:09 ` Greg KH
2005-06-08 15:56 Abhay Salunke
2005-06-08 15:17 Abhay Salunke
2005-06-08 15:56 ` Dmitry Torokhov
2005-06-08 16:02 ` Greg KH
2005-06-08 16:09 ` Dmitry Torokhov
2005-06-08 16:19 ` Greg KH
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=20050608162632.GA1588@kroah.com \
--to=greg@kroah.com \
--cc=Abhay_Salunke@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ranty@debian.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