On Mon, Jun 06, 2005 at 03:22:45PM -0500, [email protected] wrote:
> > > > 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? :)
> >
> I can sure submit a patch later but for now please accept it in the
> tree.
Heh, um, no.
> Due to scheduling issues it may not be possible for me to fix this now.
Please realize that we do not know, nor care about your scheduling
issues :)
For more details on "things you should never say on the Linux kernel
mailing list", see Randy Dunlap's very good presentation on kernel
development at:
http://www.madrone.org/mentor/linux-mentoring.pdf
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
