DRM GUD driver debug logging

[Ruben Wauters]

Hello

I was taking a look at the code for the gud driver. I am aware this
driver was recently orphaned and I wish to get up to speed on it, and
maybe with enough learning and work I can take over maintainance of it
in the future.

I noticed that in the function gud_disconnect in gud_driv.c on like 623
there is the following code

	drm_dbg(drm, "%s:\n", __func__);

checkpatch.pl marks this as unnecessary ftrace like logging, and
suggests to use ftrace instead. Since (as far as I can tell) this
effectively just prints the function name, would it not be better to
just use ftrace for debugging and remove this call all together?

While it isn't actively *harming* the code as such, it does seem a bit
unnecessary.

I'd like to know the DRM maintainers opinions. I know this particular
driver does not have a maintainer dedicated to it, so I'd like to know
the opinion of those that maintain the subsystem, and anyone else that
has any opinion.

Thank you

Ruben Wauters