netdev - Re: [PATCH V5 00/16] net: iosm: PCIe Driver for Intel M.2 Modem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sun, 13 Jun 2021 21:30:06 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     M Chetan Kumar <m.chetan.kumar@...el.com>
Cc:     netdev@...r.kernel.org, linux-wireless@...r.kernel.org,
        johannes@...solutions.net, krishna.c.sudi@...el.com,
        linuxwwan@...el.com
Subject: Re: [PATCH V5 00/16] net: iosm: PCIe Driver for Intel M.2 Modem

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