netdev - Re: [net-next v2 0/8] drivers/s390/net/ism: Add generalized interface

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 25 Jan 2023 10:00:18 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Jan Karcher <jaka@...ux.ibm.com>
Cc:     davem@...emloft.net, kuba@...nel.org, edumazet@...gle.com,
        pabeni@...hat.com, netdev@...r.kernel.org,
        linux-s390@...r.kernel.org, hca@...ux.ibm.com,
        wintera@...ux.ibm.com, wenjia@...ux.ibm.com,
        twinkler@...ux.ibm.com, raspl@...ux.ibm.com, kgraul@...ux.ibm.com,
        niho@...ux.ibm.com, pasic@...ux.ibm.com, tonylu@...ux.alibaba.com,
        guwen@...ux.alibaba.com
Subject: Re: [net-next v2 0/8] drivers/s390/net/ism: Add generalized interface

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:

On Mon, 23 Jan 2023 19:17:44 +0100 you wrote:
> Previously, there was no clean separation between SMC-D code and the ISM
> device driver.This patch series addresses the situation to make ISM available
> for uses outside of SMC-D.
> In detail: SMC-D offers an interface via struct smcd_ops, which only the
> ISM module implements so far. However, there is no real separation between
> the smcd and ism modules, which starts right with the ISM device
> initialization, which calls directly into the SMC-D code.
> This patch series introduces a new API in the ISM module, which allows
> registration of arbitrary clients via include/linux/ism.h: struct ism_client.
> Furthermore, it introduces a "pure" struct ism_dev (i.e. getting rid of
> dependencies on SMC-D in the device structure), and adds a number of API
> calls for data transfers via ISM (see ism_register_dmb() & friends).
> Still, the ISM module implements the SMC-D API, and therefore has a number
> of internal helper functions for that matter.
> Note that the ISM API is consciously kept thin for now (as compared to the
> SMC-D API calls), as a number of API calls are only used with SMC-D and
> hardly have any meaningful usage beyond SMC-D, e.g. the VLAN-related calls.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/8] net/smc: Terminate connections prior to device removal
    https://git.kernel.org/netdev/net-next/c/c40bff4132e5
  - [net-next,v2,2/8] net/ism: Add missing calls to disable bus-mastering
    https://git.kernel.org/netdev/net-next/c/462502ff9acb
  - [net-next,v2,3/8] s390/ism: Introduce struct ism_dmb
    https://git.kernel.org/netdev/net-next/c/1baedb13f1d5
  - [net-next,v2,4/8] net/ism: Add new API for client registration
    https://git.kernel.org/netdev/net-next/c/89e7d2ba61b7
  - [net-next,v2,5/8] net/smc: Register SMC-D as ISM client
    https://git.kernel.org/netdev/net-next/c/8747716f3942
  - [net-next,v2,6/8] net/smc: Separate SMC-D and ISM APIs
    https://git.kernel.org/netdev/net-next/c/9de4df7b6be1
  - [net-next,v2,7/8] s390/ism: Consolidate SMC-D-related code
    https://git.kernel.org/netdev/net-next/c/820f21009f1b
  - [net-next,v2,8/8] net/smc: De-tangle ism and smc device initialization
    https://git.kernel.org/netdev/net-next/c/8c81ba20349d

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