From: Vincent Mailhol <mailhol@kernel.org>
To: netdev@vger.kernel.org,
Stephen Hemminger <stephen@networkplumber.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Oliver Hartkopp <socketcan@hartkopp.net>,
David Ahern <dsahern@kernel.org>
Cc: "Rakuram Eswaran" <rakuram.e96@gmail.com>,
"Stéphane Grosjean" <stephane.grosjean@free.fr>,
linux-kernel@vger.kernel.org, linux-can@vger.kernel.org,
"Vincent Mailhol" <mailhol@kernel.org>
Subject: [PATCH iproute2-next v2 0/7] iplink_can: add CAN XL support
Date: Mon, 01 Dec 2025 23:55:08 +0100 [thread overview]
Message-ID: <20251201-canxl-netlink-v2-0-dadfac811872@kernel.org> (raw)
Support for CAN XL was added to the kernel in [1]. This series is the
iproute2 counterpart.
Patches #1 to #3 are clean-ups. They refactor iplink_can's
print_usage()'s function.
Patches #4 to #7 add the CAN XL interface to iplink_can.
[1] commit 113aa9101a91 ("Merge patch series "can: netlink: add CAN XL support")
Link: https://git.kernel.org/netdev/net-next/c/113aa9101a91
Signed-off-by: Vincent Mailhol <mailhol@kernel.org>
---
Changes in v2:
- add the "iproute2-next" prefix to the patches
- s/matches/strcmp/g in can_parse_opt()
- Patch #3: "s/mili second/milisecond/g" and "s/nano second/nanosecond/g"
- Patch #6: s/XL-TMS/TMS/g in print_ctrlmode()
- Patch #7: Remove a double space in patch description
Link to v1: https://lore.kernel.org/r/20251129-canxl-netlink-v1-0-96f2c0c54011@kernel.org
---
Vincent Mailhol (7):
iplink_can: print_usage: fix the text indentation
iplink_can: print_usage: change unit for minimum time quanta to mtq
iplink_can: print_usage: describe the CAN bittiming units
iplink_can: add the "restricted" option
iplink_can: add initial CAN XL interface
iplink_can: add CAN XL's "tms" option
iplink_can: add CAN XL's PWM interface
ip/iplink_can.c | 338 ++++++++++++++++++++++++++++++++++++++++++++++++++++----
1 file changed, 314 insertions(+), 24 deletions(-)
---
base-commit: a4861e4576d84c12122235d0abb7899784a6f75a
change-id: 20250921-canxl-netlink-dd17ae310258
Best regards,
--
Vincent Mailhol <mailhol@kernel.org>
next reply other threads:[~2025-12-01 22:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 22:55 Vincent Mailhol [this message]
2025-12-01 22:55 ` [PATCH iproute2-next v2 1/7] iplink_can: print_usage: fix the text indentation Vincent Mailhol
2025-12-01 22:55 ` [PATCH iproute2-next v2 2/7] iplink_can: print_usage: change unit for minimum time quanta to mtq Vincent Mailhol
2025-12-01 22:55 ` [PATCH iproute2-next v2 3/7] iplink_can: print_usage: describe the CAN bittiming units Vincent Mailhol
2025-12-01 22:55 ` [PATCH iproute2-next v2 4/7] iplink_can: add the "restricted" option Vincent Mailhol
2025-12-01 22:55 ` [PATCH iproute2-next v2 5/7] iplink_can: add initial CAN XL interface Vincent Mailhol
2025-12-02 0:38 ` Stephen Hemminger
2025-12-02 22:30 ` Vincent Mailhol
2025-12-01 22:55 ` [PATCH iproute2-next v2 6/7] iplink_can: add CAN XL's "tms" option Vincent Mailhol
2025-12-01 22:55 ` [PATCH iproute2-next v2 7/7] iplink_can: add CAN XL's PWM interface Vincent Mailhol
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=20251201-canxl-netlink-v2-0-dadfac811872@kernel.org \
--to=mailhol@kernel.org \
--cc=dsahern@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=rakuram.e96@gmail.com \
--cc=socketcan@hartkopp.net \
--cc=stephane.grosjean@free.fr \
--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
all inboxes | Powered by JetHome®