On Wed, 13 Jun 2007 18:53:30 +0200, Lukas Razik <linux@xxxxxxxxxx> wrote: > On Wed, 13 Jun 2007 18:12:14 +0200, Lukas Razik <linux@xxxxxxxxxx> wrote: >> Hello! >> >> If I do the following under v2.6.21.3: >> >> ... >> struct completion thread_complete; >> init_complete(&thread_complete); >> >> kthread_run(thread_action, (void *)thread_complete, "thread); >> >> wait_for_completion(&thread_complete); >> ... >> >> ...then it waits... >> But if thread_action() after a while calls complete(&thread_complete) > then >> I geht an error (something with "__wake_up_common"). >> >> So, how should I initialize 'struct completion thread_complete' if I > don't >> want to use DECLARE_COMPLETION() (because thread_complete should be the >> member of a struct)? >> >> Regards and many thanks for your answers! >> Lukas >> >> >> >> > > > Hi again! > > Sorry, but I mean init_completion() instead of init_complete() > > Regards, > Lukas Hi! The usage is correct but I had another bug which I've _finally_ solved... :-) Best regards, Lukas -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
