I appreciate the suggestions.

I simply grepped this piece of code by chance while looking at an
actual sparse warning somewhere else. There's no
symptoms and I'm not sure under what conditions this debug statement
is printed nor why/when. But this is an obviously buggy
code only impacting debug/trace statements, but it could become more
serious if/when someone wants to rely on this return code
in the future. I'll expand the terse description and resubmit.

Cheers,
Tolga
_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Reply via email to