On Wed, May 5, 2010 at 12:18 AM, Anatolij Gustschin <agust@denx.de> wrote:
Thanks for being so quick to pick up on this Anatolij. I've been
traveling and not able to respond to stuff. I see that Greg has
already picked this up (thanks Greg!), but FWIW:
Acked-by: Grant Likely <grant.likely@secretlab.ca>
Actually, now that I look, this fix needs to go into Linus' tree right
away (not just linux-next) since the offending patch went in during
the 2.6.34 merge window.
Greg, I can either pick this up and push it out to Linus tomorrow, or
let you do it. Whichever you prefer. Let me know so I don't cause
conflicts in your tree.
On another note, this patch isn't actually the right fix, but that's
because this driver is such a horribly bad example of handling private
data that doing the right thing requires some re-architecting. The
driver should not need any of that extra code in the module_init hook.
For now this is the best thing to do, but I'll dig into it tomorrow
and see if I can churn out a patch to fix it properly for the 2.6.35
merge window.
Cheers and thanks,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--