[RFC iproute 4/5] tcp_metrics: use print_luint

[Stephen Hemminger]

Metrics are long unsigned, so use correct print function.

Signed-off-by: Stephen Hemminger <step...@networkplumber.org>
---
 ip/tcp_metrics.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ip/tcp_metrics.c b/ip/tcp_metrics.c
index 72dc980c92a6..3b82a4e1d2f2 100644
--- a/ip/tcp_metrics.c
+++ b/ip/tcp_metrics.c
@@ -139,7 +139,7 @@ static void print_tcp_metrics(struct rtattr *a)
 
                print_uint(PRINT_JSON, name, NULL, val);
                print_string(PRINT_FP, NULL, " %s ", name);
-               print_uint(PRINT_FP, NULL, "%lu", val);
+               print_luint(PRINT_FP, NULL, "%lu", val);
        }
 
        if (rtt) {
-- 
2.17.0