From: Stephen Hemminger <stephen@networkplumber.org>
To: "Remigiusz Kołłątaj" <remigiusz.kollataj@mobica.com>
Cc: netdev@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: [PATCH iproute2] ip: add handling for new CAN netlink interface
Date: Mon, 22 May 2017 13:37:05 -0700 [thread overview]
Message-ID: <20170522133705.57e13882@xeon-e3> (raw)
In-Reply-To: <20170519125449.7214-1-remigiusz.kollataj@mobica.com>
On Fri, 19 May 2017 14:54:49 +0200
Remigiusz Kołłątaj <remigiusz.kollataj@mobica.com> wrote:
> This patch adds handling for new CAN netlink interface introduced in
> 4.11 kernel:
> - IFLA_CAN_TERMINATION,
> - IFLA_CAN_TERMINATION_CONST,
> - IFLA_CAN_BITRATE_CONST,
> - IFLA_CAN_DATA_BITRATE_CONST
>
> Output example:
> $ip -d link show can0
> 6: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN mode DEFAULT group default qlen 10
> link/can promiscuity 0
> can state STOPPED (berr-counter tx 0 rx 0) restart-ms 0
> bitrate 80000
> [ 20000, 33333, 50000, 80000, 83333, 100000,
> 125000, 150000, 175000, 200000, 225000, 250000,
> 275000, 300000, 500000, 625000, 800000, 1000000 ]
> termination 0 [ 0, 120 ]
> clock 0numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
>
> Signed-off-by: Remigiusz Kołłątaj <remigiusz.kollataj@mobica.com>
What is output without the -d flag?
In general iproute2 show commands are designed to be invertable.
I.e the show command looks like the same command to set.
Printing the bitrates and the format of the state output looks quite different
than the set command. Is it limited to detail (-d)?
next prev parent reply other threads:[~2017-05-22 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 12:54 [PATCH iproute2] ip: add handling for new CAN netlink interface Remigiusz Kołłątaj
2017-05-22 20:37 ` Stephen Hemminger [this message]
2017-05-23 8:47 ` Kołłątaj, Remigiusz
2017-05-31 0:40 ` Stephen Hemminger
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=20170522133705.57e13882@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=remigiusz.kollataj@mobica.com \
/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