> Please disregard my concern about consistency, I was missing something,
> not you
Sorry if it came out as out of place. I just feel like starting to
introduce the macro
in places where the function name is outright wrong might be a good idea,
since
if the function was changed once it makes sense
>Not sure if touching all error messages for __func__ is worth it or just
>too much churn in the end.
He already converted some so I don't see a reason to not introduce at least
that diff. If someone comes across something, he could just fix it then and
there if this issue is well-known.
On Tue,