Comment 6 for bug 86778

I marked the issue as "confirmed" myself because I am confident of what I said, and that the trivial change I suggested fixes the problem. And any competent C programmer can agree on that, after reading my report.

I avoided whining for long time, but the only conclusion I can give to this is that you have no competent C programmer, in your bug tracking team. Actually, not enough to even read bug reports.

Given that I have sent two kernel bug reports containing the solution, that I'm a kernel hacker myself, and that after more than one year the bug is still open, how will you be able to handle _real_ bug reports, where finding the problem is damn difficult?