netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Loic Poulain <loic.poulain@linaro.org>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
	m.chetan.kumar@intel.com, johannes.berg@intel.com,
	leon@kernel.org, ryazanov.s.a@gmail.com, parav@nvidia.com
Subject: Re: [PATCH net-next v3 0/4] net: Add WWAN link creation support
Date: Sat, 12 Jun 2021 21:10:25 +0000	[thread overview]
Message-ID: <162353222513.27672.3139028019417802781.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1623486057-13075-1-git-send-email-loic.poulain@linaro.org>

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



      parent reply	other threads:[~2021-06-12 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12  8:20 [PATCH net-next v3 0/4] net: Add WWAN link creation support Loic Poulain
2021-06-12  8:20 ` [PATCH net-next v3 1/4] rtnetlink: add alloc() method to rtnl_link_ops Loic Poulain
2021-06-12  8:20 ` [PATCH net-next v3 2/4] rtnetlink: add IFLA_PARENT_[DEV|DEV_BUS]_NAME Loic Poulain
2021-06-12  8:20 ` [PATCH net-next v3 3/4] wwan: add interface creation support Loic Poulain
2021-06-12  8:20 ` [PATCH net-next v3 4/4] net: mhi_net: Register wwan_ops for link creation Loic Poulain
2021-06-12 21:10 ` patchwork-bot+netdevbpf [this message]

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=162353222513.27672.3139028019417802781.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=johannes.berg@intel.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=m.chetan.kumar@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=parav@nvidia.com \
    --cc=ryazanov.s.a@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).