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: linux-kernel@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: [PATCH 0/7] iplink_can: add CAN XL support
Date: Sat, 29 Nov 2025 16:38:25 +0100 [thread overview]
Message-ID: <e2ab2f04-35fc-462f-b4d0-a8429b765111@kernel.org> (raw)
In-Reply-To: <20251129-canxl-netlink-v1-0-96f2c0c54011@kernel.org>
On 29/11/2025 at 16:29, Vincent Mailhol wrote:
> 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>
And just after sending, I realized that I forgot to add the "iproute2-next"
prefix in the patch subjects.
Well, I will wait for the comments first and resent on Monday with the correct tag.
Yours sincerely,
Vincent Mailhol
prev parent reply other threads:[~2025-11-29 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 15:29 [PATCH 0/7] iplink_can: add CAN XL support Vincent Mailhol
2025-11-29 15:29 ` [PATCH 1/7] iplink_can: print_usage: fix the text indentation Vincent Mailhol
2025-11-29 15:29 ` [PATCH 2/7] iplink_can: print_usage: change unit for minimum time quanta to mtq Vincent Mailhol
2025-11-29 15:29 ` [PATCH 3/7] iplink_can: print_usage: describe the CAN bittiming units Vincent Mailhol
2025-11-29 15:29 ` [PATCH 4/7] iplink_can: add the "restricted" option Vincent Mailhol
2025-11-29 17:03 ` Stephen Hemminger
2025-11-29 15:29 ` [PATCH 5/7] iplink_can: add initial CAN XL support Vincent Mailhol
2025-11-29 17:04 ` Stephen Hemminger
2025-11-29 23:13 ` Vincent Mailhol
2025-11-29 15:29 ` [PATCH 6/7] iplink_can: add CAN XL's "tms" option Vincent Mailhol
2025-11-29 17:21 ` Oliver Hartkopp
2025-11-29 23:16 ` Vincent Mailhol
2025-11-29 15:29 ` [PATCH 7/7] iplink_can: add CAN XL's PWM interface Vincent Mailhol
2025-11-29 17:26 ` Oliver Hartkopp
2025-11-29 15:38 ` Vincent Mailhol [this message]
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=e2ab2f04-35fc-462f-b4d0-a8429b765111@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=socketcan@hartkopp.net \
--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).