From: Mika Westerberg Date: Mon, 29 Jun 2020 17:23:58 +0000 (+0300) Subject: thunderbolt: No need to warn in TB_CFG_ERROR_INVALID_CONFIG_SPACE X-Git-Tag: microblaze-v5.11~128^2~26^2~9 X-Git-Url: http://git.monstr.eu/?p=linux-2.6-microblaze.git;a=commitdiff_plain;h=fa1653d99cc8296628e4fa949afad6f87889d14b thunderbolt: No need to warn in TB_CFG_ERROR_INVALID_CONFIG_SPACE This may be returned for example when accessing some of the vendor specific capabilities. It is not fatal by any means so instead of WARN() just log it as debug level. The caller gets error back anyway and is expected to handle it accordingly. Signed-off-by: Mika Westerberg Reviewed-by: Greg Kroah-Hartman --- diff --git a/drivers/thunderbolt/ctl.c b/drivers/thunderbolt/ctl.c index 394a23ce6ca4..2364efa23991 100644 --- a/drivers/thunderbolt/ctl.c +++ b/drivers/thunderbolt/ctl.c @@ -266,9 +266,8 @@ static void tb_cfg_print_error(struct tb_ctl *ctl, * Invalid cfg_space/offset/length combination in * cfg_read/cfg_write. */ - tb_ctl_WARN(ctl, - "CFG_ERROR(%llx:%x): Invalid config space or offset\n", - res->response_route, res->response_port); + tb_ctl_dbg(ctl, "%llx:%x: invalid config space or offset\n", + res->response_route, res->response_port); return; case TB_CFG_ERROR_NO_SUCH_PORT: /*