From: Greg KH <greg@kroah.com>
To: Abhay_Salunke@Dell.com
Cc: marcel@holtmann.org, linux-kernel@vger.kernel.org, akpm@osdl.org,
Matt_Domsch@Dell.com
Subject: Re: [patch 2.6.12-rc3] dell_rbu: Resubmitting patch for new DellBIOS update driver
Date: Mon, 6 Jun 2005 13:12:38 -0700 [thread overview]
Message-ID: <20050606201238.GA13214@kroah.com> (raw)
In-Reply-To: <367215741E167A4CA813C8F12CE0143B3ED3AD@ausx2kmpc115.aus.amer.dell.com>
On Mon, Jun 06, 2005 at 03:01:04PM -0500, Abhay_Salunke@Dell.com wrote:
> > Ok, in re-reading the firmware code, you are correct, it will still
> > timeout in 10 seconds and call your callback.
> >
> > Which, in my opinion, is wrong. We should have some way to say "wait
> > forever". Care to change the firmware_class.c code to support this?
> Will give it a try. So far the request_firmware code calls
> kobject_hotplug with action as KOBJ_ADD. It invokes a hotplug script
> form user mode. I guess we need to have some reverse mechanism which is
> invoked when a user writes to the file.
Why? Your completion function should be called when the file is closed,
right?
> > I was assuming that this would wait forever, and is why I pointed you
> in
> > this direction. Sorry about the confusion here.
> >
> I guess the earlier method of request_firmware would work out as is with
> the only disadvantage of the user having to depend on hotplug mechanism
> and echoing firmware name.
> Let me know if that is acceptable till we find a solution to wait for
> ever without using hotplug stuff.
Why not fix the firmware_class.c code now? :)
thanks,
greg k-h
next prev parent reply other threads:[~2005-06-06 20:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 20:01 [patch 2.6.12-rc3] dell_rbu: Resubmitting patch for new DellBIOS update driver Abhay_Salunke
2005-06-06 20:12 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 14:47 Abhay_Salunke
2005-06-07 15:01 ` Greg KH
2005-06-06 20:22 Abhay_Salunke
2005-06-06 20:35 ` Greg KH
2005-06-06 18:54 Abhay_Salunke
2005-06-06 19:22 ` Greg KH
2005-06-06 16:27 Abhay_Salunke
2005-06-06 18:16 ` Greg KH
2005-06-03 19:57 Abhay_Salunke
2005-06-03 20:33 ` Greg KH
2005-06-03 19:00 Abhay_Salunke
2005-06-03 19:29 ` Greg KH
2005-06-03 13:30 Abhay_Salunke
2005-06-03 16:53 ` Marcel Holtmann
2005-06-03 18:03 ` Greg KH
2005-06-02 22:25 Abhay_Salunke
2005-06-02 22:45 ` Marcel Holtmann
2005-06-02 22:50 ` Andrew Morton
2005-06-03 5:19 ` Greg KH
2005-05-23 15:36 Abhay_Salunke
2005-05-23 15:50 ` 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=20050606201238.GA13214@kroah.com \
--to=greg@kroah.com \
--cc=Abhay_Salunke@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.