VVL already prints its messages using configurable settings. there's no
reason for zink to unconditionally repeat them immediately after
cc: mesa-stable
Reviewed-by: Dave Airlie <airlied@redhat.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13633>
static void
zink_error(const char *msg)
{
- fprintf(stderr, "zink ERR: '%s'\n", msg);
}
static void
zink_warn(const char *msg)
{
- fprintf(stderr, "zink WRN: '%s'\n", msg);
}
static void
zink_info(const char *msg)
{
- fprintf(stderr, "zink NFO: '%s'\n", msg);
}
static void
zink_msg(const char *msg)
{
- fprintf(stderr, "zink MSG: '%s'\n", msg);
}
static VKAPI_ATTR VkBool32 VKAPI_CALL