Comment 304 for bug 446146

Just curious; for me it still does not work with the latest kernel (2.6.31-15-generic) and e169. Is this considered confirmed behaviour, and if so, should the status not be changed from "fix commited" to something else?. Or should I file this bug somewhere else? Are there any e169 users for whom it works out of the box now?? Are developers thinking they solved the problem already?