thunderbolt: Changes for v6.20 merge window

This includes following USB4/Thunderbolt changes for the v6.20 merge
 window:
 
   - Tiny documentation update
   - Switch to use tb_warn() when logging path activation failures.
 
 Both have been in linux-next with no reported issues.
 -----BEGIN PGP SIGNATURE-----
 
 iQJUBAABCgA+FiEEVTdhRGBbNzLrSUBaAP2fSd+ZWKAFAmmBj3cgHG1pa2Eud2Vz
 dGVyYmVyZ0BsaW51eC5pbnRlbC5jb20ACgkQAP2fSd+ZWKA7YxAAiRORf4fN88qA
 OaHZvhYh0L2KzIHptrlkQEq3D7QyogXtSvZtCUJdFb0ZxHh1Zg/SQx4SZYWBSkiB
 PxvUB0xx72Pk4ki3JUyoJSgJQqr4BKYCd6kq5t8derw63HOhqT3+UwoezPjzorot
 poS/7YQH/LaNHL76E83F9JWnW8viMfEmhQsAVEpvM9SkEpO5mEyBbcvLeNbaFuR/
 Jzw8AbfW5cTFXt2bkxaIYGADeBrKP99Ugg7C6CmiUOcbMwqA3Nnl3sKfsF/iV0C1
 NTaMe5rdGCy0VXThRvT/S3vs1otuDw/Gw0p940EvarY36NlsIVT75iFIvG4gGLDH
 waX5+JCbJalMrF5lmRgqveSZIVAZYf6mEy1VDJCb7yFf+8sTu2S42fSFA1bszBnl
 HvYI2iAfbiIFY4rBUca+oOh5LZWACsupa4dHAlyR489IOXblFiPsWlk/LtKaGu77
 qs1GJdLyBZM9w/HZlfYcNrBK6WAJDZ8bhwHTghJkg6OOPFRllYOPYe4VtjrgGulI
 nufwXE71eYQMq3NsUbrN5WKylYXapuyaL+EW42y6hZCNWYKbRpwIkIeGp27fAse9
 rWku1FN4D2450LjVrx+wv3R6gHN4ieXbtijDYzM8SdPWpjaOwkuGe53LPqIpzaVd
 WEkra9C+G5UxZrwGYOXXr7k4swAjUJU=
 =Di/y
 -----END PGP SIGNATURE-----

Merge tag 'thunderbolt-for-v6.20-rc1' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt into usb-next

Mika writes:

thunderbolt: Changes for v6.20 merge window

This includes following USB4/Thunderbolt changes for the v6.20 merge
window:

  - Tiny documentation update
  - Switch to use tb_warn() when logging path activation failures.

Both have been in linux-next with no reported issues.

* tag 'thunderbolt-for-v6.20-rc1' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt:
  thunderbolt: Log path activation failures without WARN backtraces
  docs: admin-guide: thunderbolt: Replace ifconfig with ip
This commit is contained in:
Greg Kroah-Hartman 2026-02-05 17:05:32 +01:00
commit 917ad8a665
2 changed files with 2 additions and 2 deletions

View File

@ -370,7 +370,7 @@ is built-in to the kernel image, there is no need to do anything.
The driver will create one virtual ethernet interface per Thunderbolt
port which are named like ``thunderbolt0`` and so on. From this point
you can either use standard userspace tools like ``ifconfig`` to
you can either use standard userspace tools like ``ip`` to
configure the interface or let your GUI handle it automatically.
Forcing power

View File

@ -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;
}