On Thu, 28 Jul 2005, Pavel Machek wrote: > > process. It may also allow changing values that so far cannot be > > changed from the outside in the task struct by running a function > > in the context of the process. > > Well, we really need slightly more from "running in process context": > we also need "no locks held" for swsusp. (But other uses probably do, > too?)
Other uses also need "no locks held". > I guess I'd prefer if you left "refrigerator()" and "try_to_freeze()" > functions in; there are about 1000 drivers that know/use them, and > some patches are probably in the queue.... Yeah but then other uses also could benefit from that. - 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/
