From: Jakub Kicinski <kuba@kernel.org>
To: stephen@networkplumber.org, dsahern@gmail.com
Cc: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: [PACTH iproute2] ip: align the name of the 'nohandler' stat
Date: Fri, 30 Apr 2021 20:08:54 -0700 [thread overview]
Message-ID: <20210501030854.529712-1-kuba@kernel.org> (raw)
Before:
RX: bytes packets errors dropped missed mcast
8848233056 8548168 0 0 0 0
RX errors: length crc frame fifo overrun nohandler
0 0 0 0 0 101
TX: bytes packets errors dropped carrier collsns compressed
1142925945 4683483 0 0 0 0 101
TX errors: aborted fifo window heartbeat transns
0 0 0 0 14
After:
RX: bytes packets errors dropped missed mcast
8848297833 8548461 0 0 0 0
RX errors: length crc frame fifo overrun nohandler
0 0 0 0 0 101
TX: bytes packets errors dropped carrier collsns compressed
1143049820 4683865 0 0 0 0 101
TX errors: aborted fifo window heartbeat transns
0 0 0 0 14
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
ip/ipaddress.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ip/ipaddress.c b/ip/ipaddress.c
index cfb24f5c1e34..8783b70d81e2 100644
--- a/ip/ipaddress.c
+++ b/ip/ipaddress.c
@@ -757,7 +757,7 @@ static void __print_link_stats(FILE *fp, struct rtattr *tb[])
if (show_stats > 1) {
fprintf(fp, "%s", _SL_);
fprintf(fp, " RX errors: length crc frame fifo overrun%s%s",
- s->rx_nohandler ? " nohandler" : "", _SL_);
+ s->rx_nohandler ? " nohandler" : "", _SL_);
fprintf(fp, " ");
print_num(fp, 8, s->rx_length_errors);
print_num(fp, 7, s->rx_crc_errors);
--
2.31.1
next reply other threads:[~2021-05-01 3:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 3:08 Jakub Kicinski [this message]
2021-05-06 14:41 ` [PACTH iproute2] ip: align the name of the 'nohandler' stat David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210501030854.529712-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).