summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorChia-Lin Kao (AceLan) <acelan.kao@canonical.com>2026-01-02 11:19:05 +0800
committerMika Westerberg <mika.westerberg@linux.intel.com>2026-01-05 12:14:43 +0100
commit062191adfde0b11b01656ea6db51a9385fa3d104 (patch)
treec6bd02558d9cf398118f99a893267833a0a27332 /drivers
parent0c90fd379bb5d2eb02051f312a7bb45d56e006bf (diff)
thunderbolt: Log path activation failures without WARN backtraces
tb_path_activate() currently logs failures with tb_WARN(), which triggers a stack trace. Transient conditions such as lane bonding or Type-C link hiccups can fail path activation briefly, and the resulting backtraces are noisy without aiding diagnosis. Switch to tb_warn() for all path activation failures. The error code is already returned to callers, and the warning still shows the message without the backtrace. Signed-off-by: Chia-Lin Kao (AceLan) <acelan.kao@canonical.com> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/thunderbolt/path.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/thunderbolt/path.c b/drivers/thunderbolt/path.c
index f9b11dadfbdd..50659bd55d7b 100644
--- a/drivers/thunderbolt/path.c
+++ b/drivers/thunderbolt/path.c
@@ -586,7 +586,7 @@ int tb_path_activate(struct tb_path *path)
tb_dbg(path->tb, "%s path activation complete\n", path->name);
return 0;
err:
- tb_WARN(path->tb, "%s path activation failed\n", path->name);
+ tb_warn(path->tb, "%s path activation failed: %d\n", path->name, res);
return res;
}