From: patchwork-bot+netdevbpf@kernel.org
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
dsahern@gmail.com, linux-can@vger.kernel.org, mkl@pengutronix.de,
socketcan@hartkopp.net, mbro1689@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH iproute2-next v1 0/6] iplink_can: preparation before introduction of CAN XL
Date: Mon, 18 Nov 2024 17:00:30 +0000 [thread overview]
Message-ID: <173194923075.4109060.18408610499610779344.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241112172812.590665-8-mailhol.vincent@wanadoo.fr>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 13 Nov 2024 02:27:50 +0900 you wrote:
> An RFC was sent last weekend to kick-off the discussion of the
> introduction of CAN XL: [1] for the kernel side and [2] for the
> iproute2 interface. While the series received some positive feedback,
> it is far from completion. Some work is still needed to:
>
> - adjust the nesting of the IFLA_CAN_XL_DATA_BITTIMING_CONST in the
> netlink interface
>
> [...]
Here is the summary with links:
- [iproute2-next,v1,1/6] iplink_can: remove unused FILE *f parameter in three functions
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=df72757907f3
- [iproute2-next,v1,2/6] iplink_can: reduce the visibility of tdc in can_parse_opt()
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=3bd5fb4d57aa
- [iproute2-next,v1,3/6] iplink_can: remove newline at the end of invarg()'s messages
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=9b1f33d5a46d
- [iproute2-next,v1,4/6] iplink_can: use invarg() instead of fprintf()
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=68aaea862838
- [iproute2-next,v1,5/6] iplink_can: add struct can_tdc
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=aac087a0108b
- [iproute2-next,v1,6/6] iplink_can: rename dbt into fd_dbt in can_parse_opt()
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=3f2ab9d6070e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-18 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 17:27 [PATCH iproute2-next v1 0/6] iplink_can: preparation before introduction of CAN XL Vincent Mailhol
2024-11-12 17:27 ` [PATCH iproute2-next v1 1/6] iplink_can: remove unused FILE *f parameter in three functions Vincent Mailhol
2024-11-12 17:27 ` [PATCH iproute2-next v1 2/6] iplink_can: reduce the visibility of tdc in can_parse_opt() Vincent Mailhol
2024-11-12 17:27 ` [PATCH iproute2-next v1 3/6] iplink_can: remove newline at the end of invarg()'s messages Vincent Mailhol
2024-11-12 17:27 ` [PATCH iproute2-next v1 4/6] iplink_can: use invarg() instead of fprintf() Vincent Mailhol
2024-11-12 17:27 ` [PATCH iproute2-next v1 5/6] iplink_can: add struct can_tdc Vincent Mailhol
2024-11-12 17:27 ` [PATCH iproute2-next v1 6/6] iplink_can: rename dbt into fd_dbt in can_parse_opt() Vincent Mailhol
2024-11-18 17:00 ` patchwork-bot+netdevbpf [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=173194923075.4109060.18408610499610779344.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mbro1689@gmail.com \
--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