From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
mailhol.vincent@wanadoo.fr
Subject: Re: [PATCH net-next 1/7] can: netlink: replace tabulation by space in assignment
Date: Tue, 10 Jun 2025 23:50:40 +0000 [thread overview]
Message-ID: <174959944075.2737769.15070024166565059236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250610094933.1593081-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Tue, 10 Jun 2025 11:46:16 +0200 you wrote:
> From: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
>
> commit cfd98c838cbe ("can: netlink: move '=' operators back to
> previous line (checkpatch fix)") inadvertently introduced a tabulation
> between the IFLA_CAN_DATA_BITTIMING_CONST array index and the equal
> sign.
>
> [...]
Here is the summary with links:
- [net-next,1/7] can: netlink: replace tabulation by space in assignment
https://git.kernel.org/netdev/net-next/c/d08ad6c8613b
- [net-next,2/7] can: bittiming: rename CAN_CTRLMODE_TDC_MASK into CAN_CTRLMODE_FD_TDC_MASK
https://git.kernel.org/netdev/net-next/c/bee7e3322a28
- [net-next,3/7] can: bittiming: rename can_tdc_is_enabled() into can_fd_tdc_is_enabled()
https://git.kernel.org/netdev/net-next/c/23c0dc95bfa8
- [net-next,4/7] can: netlink: can_changelink(): rename tdc_mask into fd_tdc_flag_provided
https://git.kernel.org/netdev/net-next/c/527b99f44def
- [net-next,5/7] documentation: networking: can: Document alloc_candev_mqs()
(no matching commit)
- [net-next,6/7] can: add drop reasons in the receive path of AF_CAN
https://git.kernel.org/netdev/net-next/c/127c49624a09
- [net-next,7/7] can: add drop reasons in CAN protocols receive path
https://git.kernel.org/netdev/net-next/c/81807451c2a6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-06-10 23:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 9:46 [PATCH net-next 0/7] pull-request: can-next 2025-06-10 Marc Kleine-Budde
2025-06-10 9:46 ` [PATCH net-next 1/7] can: netlink: replace tabulation by space in assignment Marc Kleine-Budde
2025-06-10 23:50 ` patchwork-bot+netdevbpf [this message]
2025-06-10 9:46 ` [PATCH net-next 2/7] can: bittiming: rename CAN_CTRLMODE_TDC_MASK into CAN_CTRLMODE_FD_TDC_MASK Marc Kleine-Budde
2025-06-10 9:46 ` [PATCH net-next 3/7] can: bittiming: rename can_tdc_is_enabled() into can_fd_tdc_is_enabled() Marc Kleine-Budde
2025-06-10 9:46 ` [PATCH net-next 4/7] can: netlink: can_changelink(): rename tdc_mask into fd_tdc_flag_provided Marc Kleine-Budde
2025-06-10 9:46 ` [PATCH net-next 5/7] documentation: networking: can: Document alloc_candev_mqs() Marc Kleine-Budde
2025-06-10 9:46 ` [PATCH net-next 6/7] can: add drop reasons in the receive path of AF_CAN Marc Kleine-Budde
2025-06-10 22:50 ` Jakub Kicinski
2025-06-11 11:39 ` Davide Caratti
2025-06-10 9:46 ` [PATCH net-next 7/7] can: add drop reasons in CAN protocols receive path Marc Kleine-Budde
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=174959944075.2737769.15070024166565059236.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.