netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: M Chetan Kumar <m.chetan.kumar@intel.com>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	johannes@sipsolutions.net, krishna.c.sudi@intel.com,
	linuxwwan@intel.com
Subject: Re: [PATCH V5 00/16] net: iosm: PCIe Driver for Intel M.2 Modem
Date: Sun, 13 Jun 2021 21:30:06 +0000	[thread overview]
Message-ID: <162361980669.14320.17522019509048799009.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210613125023.18945-1-m.chetan.kumar@intel.com>

Hello:

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

On Sun, 13 Jun 2021 18:20:07 +0530 you wrote:
> The IOSM (IPC over Shared Memory) driver is a PCIe host driver implemented
> for linux or chrome platform for data exchange over PCIe interface between
> Host platform & Intel M.2 Modem. The driver exposes interface conforming to
> the MBIM protocol. Any front end application ( eg: Modem Manager) could
> easily manage the MBIM interface to enable data communication towards WWAN.
> 
> Intel M.2 modem uses 2 BAR regions. The first region is dedicated to Doorbell
> register for IRQs and the second region is used as scratchpad area for book
> keeping modem execution stage details along with host system shared memory
> region context details. The upper edge of the driver exposes the control and
> data channels for user space application interaction. At lower edge these data
> and control channels are associated to pipes. The pipes are lowest level
> interfaces used over PCIe as a logical channel for message exchange. A single
> channel maps to UL and DL pipe and are initialized on device open.
> 
> [...]

Here is the summary with links:
  - [V5,01/16] net: iosm: entry point
    https://git.kernel.org/netdev/net-next/c/7e98d785ae61
  - [V5,02/16] net: iosm: irq handling
    https://git.kernel.org/netdev/net-next/c/7f41ce085de0
  - [V5,03/16] net: iosm: mmio scratchpad
    https://git.kernel.org/netdev/net-next/c/dc0514f5d828
  - [V5,04/16] net: iosm: shared memory IPC interface
    https://git.kernel.org/netdev/net-next/c/3670970dd8c6
  - [V5,05/16] net: iosm: shared memory I/O operations
    https://git.kernel.org/netdev/net-next/c/edf6423c0403
  - [V5,06/16] net: iosm: channel configuration
    https://git.kernel.org/netdev/net-next/c/30ebda7a313d
  - [V5,07/16] net: iosm: wwan port control device
    https://git.kernel.org/netdev/net-next/c/10685b6e9868
  - [V5,08/16] net: iosm: bottom half
    https://git.kernel.org/netdev/net-next/c/3b575260cb86
  - [V5,09/16] net: iosm: multiplex IP sessions
    https://git.kernel.org/netdev/net-next/c/51c45fa95435
  - [V5,10/16] net: iosm: encode or decode datagram
    https://git.kernel.org/netdev/net-next/c/9413491e20e1
  - [V5,11/16] net: iosm: power management
    https://git.kernel.org/netdev/net-next/c/be8c936e540f
  - [V5,12/16] net: iosm: shared memory protocol
    https://git.kernel.org/netdev/net-next/c/faed4c6f6f48
  - [V5,13/16] net: iosm: protocol operations
    https://git.kernel.org/netdev/net-next/c/64516f633bfd
  - [V5,14/16] net: iosm: uevent support
    https://git.kernel.org/netdev/net-next/c/110e6e02eb19
  - [V5,15/16] net: iosm: net driver
    https://git.kernel.org/netdev/net-next/c/2a54f2c77934
  - [V5,16/16] net: iosm: infrastructure
    https://git.kernel.org/netdev/net-next/c/f7af616c632e

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-13 21:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 12:50 [PATCH V5 00/16] net: iosm: PCIe Driver for Intel M.2 Modem M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 01/16] net: iosm: entry point M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 02/16] net: iosm: irq handling M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 03/16] net: iosm: mmio scratchpad M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 04/16] net: iosm: shared memory IPC interface M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 05/16] net: iosm: shared memory I/O operations M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 06/16] net: iosm: channel configuration M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 07/16] net: iosm: wwan port control device M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 08/16] net: iosm: bottom half M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 09/16] net: iosm: multiplex IP sessions M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 10/16] net: iosm: encode or decode datagram M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 11/16] net: iosm: power management M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 12/16] net: iosm: shared memory protocol M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 13/16] net: iosm: protocol operations M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 14/16] net: iosm: uevent support M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 15/16] net: iosm: net driver M Chetan Kumar
2021-06-13 12:50 ` [PATCH V5 16/16] net: iosm: infrastructure M Chetan Kumar
2021-06-13 16:01   ` Leon Romanovsky
2021-06-13 21:30 ` 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=162361980669.14320.17522019509048799009.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=krishna.c.sudi@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwwan@intel.com \
    --cc=m.chetan.kumar@intel.com \
    --cc=netdev@vger.kernel.org \
    /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).