Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Sat, 12 Jun 2021 10:20:53 +0200 you wrote:

Most of the modern WWAN modems are able to support multiple network
contexts, allowing user to connect to different APNs (e.g. Internet,
MMS, etc...). These contexts are usually dynamically configured via
a control channel such as MBIM, QMI or AT.

Each context is naturally represented as a network link/device, and
the muxing of these links is usually vendor/bus specific (QMAP, MBIM,
intel iosm...). Today some drivers create a static collection of
netdevs at init time, some relies on VLAN link for associating a context
(cdc-mbim), some exposes sysfs attribute for dynamically creating
additional netdev (qmi_wwan add_mux attr) or relies on vendor specific
link type (rmnet) for performing the muxing... so there is no generic
way to handle WWAN links, making user side integration painful.

[...]

Here is the summary with links:
  - [net-next,v3,1/4] rtnetlink: add alloc() method to rtnl_link_ops
    https://git.kernel.org/netdev/net-next/c/8c713dc93ca9
  - [net-next,v3,2/4] rtnetlink: add IFLA_PARENT_[DEV|DEV_BUS]_NAME
    https://git.kernel.org/netdev/net-next/c/00e77ed8e64d
  - [net-next,v3,3/4] wwan: add interface creation support
    https://git.kernel.org/netdev/net-next/c/88b710532e53
  - [net-next,v3,4/4] net: mhi_net: Register wwan_ops for link creation
    https://git.kernel.org/netdev/net-next/c/13adac032982

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