All of lore.kernel.org
 help / color / mirror / Atom feed
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,
	socketcan@hartkopp.net,
	syzbot+5b11eccc403dd1cea9f8@syzkaller.appspotmail.com
Subject: Re: [PATCH net 01/12] can: bcm: fix locking for bcm_op runtime updates
Date: Thu, 05 Mar 2026 01:00:21 +0000	[thread overview]
Message-ID: <177267242168.2463633.16799782659117559019.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260302152755.1700177-2-mkl@pengutronix.de>

Hello:

This series was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:

On Mon,  2 Mar 2026 16:16:07 +0100 you wrote:
> From: Oliver Hartkopp <socketcan@hartkopp.net>
> 
> Commit c2aba69d0c36 ("can: bcm: add locking for bcm_op runtime updates")
> added a locking for some variables that can be modified at runtime when
> updating the sending bcm_op with a new TX_SETUP command in bcm_tx_setup().
> 
> Usually the RX_SETUP only handles and filters incoming traffic with one
> exception: When the RX_RTR_FRAME flag is set a predefined CAN frame is
> sent when a specific RTR frame is received. Therefore the rx bcm_op uses
> bcm_can_tx() which uses the bcm_tx_lock that was only initialized in
> bcm_tx_setup(). Add the missing spin_lock_init() when allocating the
> bcm_op in bcm_rx_setup() to handle the RTR case properly.
> 
> [...]

Here is the summary with links:
  - [net,01/12] can: bcm: fix locking for bcm_op runtime updates
    https://git.kernel.org/netdev/net/c/c35636e91e39
  - [net,02/12] can: dummy_can: dummy_can_init(): fix packet statistics
    https://git.kernel.org/netdev/net/c/c77bfbdd6aac
  - [net,03/12] can: mcp251x: fix deadlock in error path of mcp251x_open
    https://git.kernel.org/netdev/net/c/ab3f894de216
  - [net,04/12] can: esd_usb: add endpoint type validation
    https://git.kernel.org/netdev/net/c/968b098220e3
  - [net,05/12] can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message
    https://git.kernel.org/netdev/net/c/38a01c9700b0
  - [net,06/12] can: ucan: Fix infinite loop from zero-length messages
    https://git.kernel.org/netdev/net/c/1e446fd0582a
  - [net,07/12] can: usb: etas_es58x: correctly anchor the urb in the read bulk callback
    https://git.kernel.org/netdev/net/c/5eaad4f76826
  - [net,08/12] can: usb: f81604: handle short interrupt urb messages properly
    https://git.kernel.org/netdev/net/c/7299b1b39a25
  - [net,09/12] can: usb: f81604: handle bulk write errors properly
    https://git.kernel.org/netdev/net/c/51f94780720f
  - [net,10/12] can: usb: f81604: correctly anchor the urb in the read bulk callback
    https://git.kernel.org/netdev/net/c/952caa5da10b
  - [net,11/12] can: gs_usb: gs_can_open(): always configure bitrates before starting device
    https://git.kernel.org/netdev/net/c/2df6162785f3
  - [net,12/12] dt-bindings: net: can: nxp,sja1000: add reference to mc-peripheral-props.yaml
    https://git.kernel.org/netdev/net/c/7e1e6d684532

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2026-03-05  1:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 15:16 [PATCH net 0/12] pull-request: can 2026-03-02 Marc Kleine-Budde
2026-03-02 15:16 ` [PATCH net 01/12] can: bcm: fix locking for bcm_op runtime updates Marc Kleine-Budde
2026-03-05  1:00   ` patchwork-bot+netdevbpf [this message]
2026-03-02 15:16 ` [PATCH net 02/12] can: dummy_can: dummy_can_init(): fix packet statistics Marc Kleine-Budde
2026-03-02 15:16 ` [PATCH net 03/12] can: mcp251x: fix deadlock in error path of mcp251x_open Marc Kleine-Budde
2026-03-02 15:16 ` [PATCH net 04/12] can: esd_usb: add endpoint type validation Marc Kleine-Budde
2026-03-02 15:16 ` [PATCH net 05/12] can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message Marc Kleine-Budde
2026-03-03 14:20   ` Paolo Abeni
2026-03-03 14:33     ` Marc Kleine-Budde
2026-03-02 15:16 ` [PATCH net 06/12] can: ucan: Fix infinite loop from zero-length messages Marc Kleine-Budde
2026-03-02 15:16 ` [PATCH net 07/12] can: usb: etas_es58x: correctly anchor the urb in the read bulk callback Marc Kleine-Budde
2026-03-02 15:16 ` [PATCH net 08/12] can: usb: f81604: handle short interrupt urb messages properly Marc Kleine-Budde
2026-03-03 14:23   ` Paolo Abeni
2026-03-04  9:07     ` Greg Kroah-Hartman
2026-03-02 15:16 ` [PATCH net 09/12] can: usb: f81604: handle bulk write errors properly Marc Kleine-Budde
2026-03-02 15:16 ` [PATCH net 10/12] can: usb: f81604: correctly anchor the urb in the read bulk callback Marc Kleine-Budde
2026-03-02 15:16 ` [PATCH net 11/12] can: gs_usb: gs_can_open(): always configure bitrates before starting device Marc Kleine-Budde
2026-03-02 15:16 ` [PATCH net 12/12] dt-bindings: net: can: nxp,sja1000: add reference to mc-peripheral-props.yaml 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=177267242168.2463633.16799782659117559019.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=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    --cc=syzbot+5b11eccc403dd1cea9f8@syzkaller.appspotmail.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 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.