thunderbolt: Use correct error code with ERROR_NOT_SUPPORTED
Subsystems (2)
PATCH 1/1 thunderbolt: Use correct error code with ERROR_NOT_SUPPORTED
We check for -EOPNOTSUPP but tb_xdp_handle_error() translated it to -ENOTSUPP instead which is dealt as "transient" error and retried after a while. Fix this so that we bail out early when the other side clearly tells us it is does not support this.
Signed-off-by Mika Westerberg <[email protected]>
--- drivers/thunderbolt/xdomain.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/thunderbolt/xdomain.c +1 -1
@@ -250,7 +250,7 @@ static int tb_xdp_handle_error(const struct tb_xdp_error_response *res)case ERROR_UNKNOWN_DOMAIN :return -EIO ;case ERROR_NOT_SUPPORTED : -return -ENOTSUPP ; +return -EOPNOTSUPP ;case ERROR_NOT_READY :return -EAGAIN ;default :
Signature · 1 line
2.43.0
Mika Westerberg
AppliedQuoted 6 lines · Mika Westerberg
We check for
-EOPNOTSUPPbuttb_xdp_handle_error()translated it to-ENOTSUPPinstead which is dealt as "transient" error and retried after a while. Fix this so that we bail out early when the other side clearly tells us it is does not support this.Signed-off-by Mika Westerberg <[email protected]>
Applied to thunderbolt.git/next.