Re: [PATCH net-next 01/11] can: tcan4x5x: put tcan into sleep when removing driver

[email protected]
Newsgroups org.kernel.vger.linux-can,org.kernel.vger.netdev
Message-ID <178707850515.2219101.2097137917698542123.git-patchwork-notify@kernel.org>
Hello:

This series was applied to netdev/net-next.git (main)
by Marc Kleine-Budde <[email protected]>:

On Tue, 18 Aug 2026 01:24:28 +0200 you wrote:
> From: Sean Nyekjaer <[email protected]>
> 
> Put the tcan4x5x transceiver into sleep mode when the driver is
> removed, instead of leaving it in its current operating mode.
> This reduces power consumption(3mA@12V) once the driver is
> no longer bound to the device.
> 
> [...]

Here is the summary with links:
  - [net-next,01/11] can: tcan4x5x: put tcan into sleep when removing driver
    (no matching commit)
  - [net-next,02/11] dt-bindings: can: rockchip: add rk3588 CAN-FD compatible
    (no matching commit)
  - [net-next,03/11] can: rockchip: add RK3588 CAN support
    https://git.kernel.org/netdev/net-next/c/b7d51d9b14ee
  - [net-next,04/11] docs: ctucanfd: fix swapped colors in legend for TX buffer FSM of CTU CAN FD
    (no matching commit)
  - [net-next,05/11] can: vxcan: support per-netns device unregistration.
    (no matching commit)
  - [net-next,06/11] MAINTAINERS: Replace maintainer for Xilinx CAN driver
    (no matching commit)
  - [net-next,07/11] dt-bindings: net: can: Convert TI HECC to DT schema
    (no matching commit)
  - [net-next,08/11] dt-bindings: can: xilinx_can: Document phys property
    (no matching commit)
  - [net-next,09/11] can: m_can: Use of_property_present() for wakeup-source
    (no matching commit)
  - [net-next,10/11] drivers: gs_usb: gs_usb_probe(): fix typo in error message
    https://git.kernel.org/netdev/net-next/c/3392698d3c1d
  - [net-next,11/11] can: m_can: pci: Remove driver_data
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.