net: thunderbolt: Add comment clarifying prtcstns flags
Subsystems (2)
PATCH 1/1 net: thunderbolt: Add comment clarifying prtcstns flags
ThunderboltIP protocol currently has two flags from which we only support and set match frags ID. The first flag is reserved for full E2E flow control. Add a comment that clarifies them.
Suggested-by Yehezkel Bernat <[email protected]>
Signed-off-by Mika Westerberg <[email protected]>
--- drivers/net/thunderbolt.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/net/thunderbolt.c +4 -0
@@ -1335,6 +1335,10 @@ static int __init tbnet_init(void)tb_property_add_immediate (tbnet_dir,"prtcid" ,1 );tb_property_add_immediate (tbnet_dir,"prtcvers" ,1 );tb_property_add_immediate (tbnet_dir,"prtcrevs" ,1 ); +/* Currently only announce support for match frags ID (bit 1). Bit 0 +* is reserved for full E2E flow control which we do not support at +* the moment. +*/ tb_property_add_immediate (tbnet_dir,"prtcstns" ,TBNET_MATCH_FRAGS_ID );
Signature · 1 line
2.27.0
Quoted 9 lines · Mika Westerberg
ThunderboltIP protocol currently has two flags from which we only support and set match frags ID. The first flag is reserved for full E2E flow control. Add a comment that clarifies them.
Suggested-by Yehezkel Bernat <[email protected]>Signed-off-by Mika Westerberg <[email protected]>---
Thanks!
Reviewed-by Yehezkel Bernat <[email protected]>
From: Mika Westerberg <[email protected]>
Date: Mon, 22 Jun 2020 19:30:22 +0300
Quoted 6 lines
ThunderboltIP protocol currently has two flags from which we only support and set match frags ID. The first flag is reserved for full E2E flow control. Add a comment that clarifies them.
Suggested-by Yehezkel Bernat <[email protected]>Signed-off-by Mika Westerberg <[email protected]>
Applied, thanks.