Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni [off-list ref]:

On Sun, 01 Feb 2026 15:33:15 +0100 you wrote:

CAN bus related skbuffs (ETH_P_CAN/ETH_P_CANFD/ETH_P_CANXL) simply contain
CAN frame structs for CAN CC/FD/XL of skb->len length at skb->data. Those
CAN skbs do not have network/mac/transport headers nor other such
references for encapsulated protocols like ethernet/IP protocols.

To store data for CAN specific use-cases all CAN bus related skbuffs are
created with a 16 byte private skb headroom (struct can_skb_priv). Using
the skb headroom and accessing skb->head for this private data led to
several problems in the past likely due to "The struct can_skb_priv
business is highly unconventional for the networking stack." [1]

[...]

Here is the summary with links:
  - [net-next,v8,1/6] can: use skb hash instead of private variable in headroom
    https://git.kernel.org/netdev/net-next/c/d4fb6514ff8e
  - [net-next,v8,2/6] can: add CAN skb extension infrastructure
    https://git.kernel.org/netdev/net-next/c/96ea3a1e2d31
  - [net-next,v8,3/6] can: move ifindex to CAN skb extensions
    (no matching commit)
  - [net-next,v8,4/6] can: move frame_len to CAN skb extensions
    https://git.kernel.org/netdev/net-next/c/d2d9179751e6
  - [net-next,v8,5/6] can: remove private CAN skb headroom infrastructure
    https://git.kernel.org/netdev/net-next/c/9f10374bb024
  - [net-next,v8,6/6] can: gw: use can_gw_hops instead of sk_buff::csum_start
    https://git.kernel.org/netdev/net-next/c/3ffecc14ec7e

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