The patch was in the 2.6.36 kernel, so by nature of that, 3.0 will alsohave it, right?

> > > Oh, and then there's caca9510ff4e5 too which adds this> > > exit path to the goto out label as the rest of the function.> > > > But that was only due to other problems.> > That second one adds the goto thing to the "out:" label where the> firmware_p gets NULLed. IOW, it prepares the code for f45f3c1f3f616.> > Does that make more sense now?

Nope, sorry, still confused :)

How about, what patches are needed for the 3.0-stable kernel tree inorder to resolve these issue? Git commit ids please.